Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →How to connect and process WooCommerce data from Azure Databricks
Use CData, Azure, and Databricks to perform data engineering and data science on live WooCommerce data.
Databricks is a cloud-based service that provides data processing capabilities through Apache Spark. When paired with the CData JDBC Driver, customers can use Databricks to perform data engineering and data science on live WooCommerce data. This article walks through hosting the CData JDBC Driver in Azure, as well as connecting to and processing live WooCommerce data in Databricks.
With built-in optimized data processing, the CData JDBC driver offers unmatched performance for interacting with live WooCommerce data. When you issue complex SQL queries to WooCommerce, the driver pushes supported SQL operations, like filters and aggregations, directly to WooCommerce and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze WooCommerce data using native data types.
Install the CData JDBC Driver in Azure
To work with live WooCommerce data in Databricks, install the driver through Azure Data Lake Storage (ADLS). (Please note that the method of connecting through DBFS, which previous versions of this article described, has been deprecated, but has not published an end-of-life.)
- Upload the JDBC JAR file to a blob container of your choice (i.e. "jdbcjars" container of the "databrickslibraries" storage account).
- Fetch the Account Key from the storage account by expanding "Security + networking" and clicking on "Access Keys". Show and copy whichever of the two keys you wish to use.
- Get the JDBC JAR file's URL by navigating to Containers, opening the specific container storing the JAR, and selecting the entry for the JDBC JAR file. This should open the file's details, where there should be a convenient button to copy the URL button to clipboard. This value will look similar to the below, though the "blob" component may vary depending on storage account type:
https://databrickslibraries.blob.core.windows.net/jdbcjars/cdata.jdbc.salesforce.jar
- In the Configuration tab of your Databricks cluster, click on the Edit button and expand "Advanced options". From there, add the following Spark option (derived from the JAR URL's domain name) with your copied Account key as its value and click Confirm:
spark.hadoop.fs.azure.account.key.databrickslibraries.blob.core.windows.net
- In the Libraries tab of your Databricks cluster, click on "Install new", and select the ADLS option. Specify the ABFSS URL for the driver JAR (also derived from the JAR URL's domain name), and click Install. The ABFSS URL should resemble the below:
abfss://[email protected]/cdata.jdbc.salesforce.jar
Connect to WooCommerce from Databricks
With the JAR file installed, we are ready to work with live WooCommerce data in Databricks. Start by creating a new notebook in your workspace. Name the workbook, make sure Python is selected as the language (which should be by default), click on Connect and under General Compute select the cluster where you installed the JDBC driver (should be selected by default).
Configure the Connection to WooCommerce
Connect to WooCommerce by referencing the class for the JDBC Driver and constructing a connection string to use in the JDBC URL. Additionally, you will need to set the RTK property in the JDBC URL (unless you are using a Beta driver). You can view the licensing file included in the installation for information on how to set this property.
driver = "cdata.jdbc.woocommerce.WooCommerceDriver" url = "jdbc:woocommerce:RTK=5246...;Url=https://example.com/; ConsumerKey=ck_ec52c76185c088ecaa3145287c8acba55a6f59ad; ConsumerSecret=cs_9fde14bf57126156701a7563fc87575713c355e5; InitiateOAuth=GETANDREFRESH"
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the WooCommerce JDBC Driver. Either double-click the JAR file or execute the JAR file from the command-line.
java -jar cdata.jdbc.woocommerce.jar
Fill in the connection properties and copy the connection string to the clipboard.
WooCommerce supports the following authentication methods: one-legged OAuth1.0 Authentication and standard OAuth2.0 Authentication.
Connecting using one-legged OAuth 1.0 Authentication
Specify the following properties (NOTE: the below credentials are generated from WooCommerce settings page and should not be confused with the credentials generated by using WordPress OAuth2.0 plugin):
- ConsumerKey
- ConsumerSecret
Connecting using WordPress OAuth 2.0 Authentication
After having configured the plugin, you may connect to WooCommerce by providing the following connection properties:
In either case, set the Url property to the URL of the WooCommerce instance.
Once the connection is configured, you can load WooCommerce data as a dataframe using the CData JDBC Driver and the connection information. Check the loaded WooCommerce data by calling the display function. If you want to process data with Databricks SparkSQL, register the loaded data as a Temp View. The SparkSQL below retrieves the WooCommerce data for analysis.
The data from WooCommerce is only available in the target notebook. If you want to use it with other users, save it as a table.
Download a free, 30-day trial of the CData JDBC Driver for WooCommerce and start working with your live WooCommerce data in Azure Databricks. Reach out to our Support Team if you have any questions.
Load WooCommerce Data
remote_table = spark.read.format ( "jdbc" ) \
.option ( "driver" , driver) \
.option ( "url" , url) \
.option ( "dbtable" , "Orders") \
.load ()
Display WooCommerce Data
display (remote_table.select ("ParentId"))
Analyze WooCommerce Data in Azure Databricks
remote_table.createOrReplaceTempView ( "SAMPLE_VIEW" )
result = spark.sql("SELECT ParentId, Total FROM SAMPLE_VIEW WHERE ParentId = '3'")
remote_table.write.format ( "parquet" ) .saveAsTable ( "SAMPLE_TABLE" )