Build Azure Data Catalog-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Azure Data Catalog enables users to access live Azure Data Catalog data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Azure Data Catalog data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from Azure Data Catalog to Google BigQuery,

Upload the CData JDBC Driver for Azure Data Catalog to Google Data Fusion

Upload the CData JDBC Driver for Azure Data Catalog to your Google Data Fusion instance to work with live Azure Data Catalog data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdataazuredatacatalog-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver 👁 Image
   
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.azuredatacatalog) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.azuredatacatalog.AzureDataCatalogDriver)
   👁 Configuring the driver (Salesforce is shown.)
   
5. Click "Finish"

Connect to Azure Data Catalog Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live Azure Data Catalog data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver 👁 Adding a database source
   
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-azuredatacatalog)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for Azure Data Catalog. For example:
     
     jdbc:azuredatacatalog:RTK=5246...;InitiateOAuth=GETANDREFRESH;

     You can optionally set the following to read the different catalog data returned from Azure Data Catalog.

     <>CatalogName: Set this to the CatalogName associated with your Azure Data Catalog. To get your Catalog name, navigate to your Azure Portal home page > Data Catalog > Catalog Name

     Connect Using OAuth Authentication

     You must use OAuth to authenticate with Azure Data Catalog. OAuth requires the authenticating user to interact with Azure Data Catalog using the browser. For more information, refer to the OAuth section in the help documentation.

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the Azure Data Catalog JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.azuredatacatalog.jar
      

     Fill in the connection properties and copy the connection string to the clipboard.

     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     
   • Set Import Query to a SQL query that will extract the data you want from Azure Data Catalog, i.e.:
     SELECT * FROM Tables
   👁 Configuring the database source
   
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like azuredatacatalog-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert Azure Data Catalog data into
   👁 Configuring the BigQuery sink
   

With the Source and Sink configured, you are ready to pipe Azure Data Catalog data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Azure Data Catalog and import it into Google BigQuery. 👁 Image

While this is a simple pipeline, you can create more complex Azure Data Catalog pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Azure Data Catalog and start working with your live Azure Data Catalog data in Google Data Fusion today.