Learn more
 

Ready to get started?

Download a free trial of the Apache Spark ODBC Driver to get started:

 Download Now

Learn more:

Apache Spark Icon Apache Spark ODBC Driver

The Spark ODBC Driver is a powerful tool that allows you to connect with Apache Spark, directly from any applications that support ODBC connectivity.

The Driver maps SQL to Spark SQL, enabling direct standard SQL-92 access to Apache Spark.

In this article

Related articles

How to Use a Microsoft Access Database to Update Spark Data in Real Time


Update Spark data by creating a linked table in Microsoft Access with the CData Spark ODBC Driver.

CData ODBC drivers connect your data to any database management tool that supports Open Database Connectivity (ODBC). This includes many of the most popular productivity tools, adding new capabilities for document sharing and collaboration. Using the CData ODBC driver for Spark, you can update live Spark data in Microsoft Access; for example, you can make updates that can be immediately seen by other users.

Connect to Spark as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Set the Server, Database, User, and Password connection properties to connect to SparkSQL.

Create a Linked Table to Customers Data

Follow the steps below to create a linked table, which enables you to access live Customers data.

  1. On the External Data tab in Access, click ODBC Database.
  2. Select the option to link to the data source. A linked table will enable you to read from and write data to the Customers table.

  3. Select the CData Spark data source from the Machine Data Source tab.

  4. Select the Customers table. For more information on this table, see the "Data Model" chapter in the help documentation.

  5. Double-click the linked table to make edits. The linked table will always have up-to-date data and any changes will be reflected back to the underlying table.