ETL Google Data Catalog in Oracle Data Integrator

Leverage existing skills by using the JDBC standard to connect to Google Data Catalog: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for Google Data Catalog connects real-time Google Data Catalog data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with Google Data Catalog just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the Google Data Catalog APIs in real time instead of working with flat files.

This article covers a JDBC-based ETL -- Google Data Catalog to Oracle. After reverse engineering a data model of Google Data Catalog entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR (cdata.jdbc.googledatacatalog.jar) and .lic file (cdata.jdbc.googledatacatalog.lic), located in the installation folder, into the ODI appropriate directory:

• UNIX/Linux without Agent: ~/.odi/oracledi/userlib
• UNIX/Linux with Agent: ~/.odi/oracledi/userlib and $ODI_HOME/odi/agent/lib
• Windows without Agent: %APPDATA%\Roaming\odi\oracledi\userlib
• Windows with Agent: %APPDATA%\odi\oracledi\userlib and %APPDATA%\odi\agent\lib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of Google Data Catalog data. After reverse engineering, you can query real-time Google Data Catalog data and create mappings based on Google Data Catalog tables.

1. In ODI, connect to your repository and click New -> Model and Topology Objects. 👁 Create a New Model
   
2. On the Model screen of the resulting dialog, enter the following information:
   • Name: Enter GoogleDataCatalog.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter GoogleDataCatalog.
   • Context: Select Global.
   👁 Configuring the Model
   
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter GoogleDataCatalog.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.googledatacatalog.GoogleDataCatalogDriver
   • URL: Enter the JDBC URL containing the connection string.

     Google Data Catalog uses the OAuth authentication standard. Authorize access to Google APIs on behalf on individual users or on behalf of users in a domain.

     Before connecting, specify the following to identify the organization and project you would like to connect to:

     • OrganizationId: The ID associated with the Google Cloud Platform organization resource you would like to connect to. Find this by navigating to the cloud console.

       Click the project selection drop-down, and select your organization from the list. Then, click More -> Settings. The organization ID is displayed on this page.

     • ProjectId: The ID associated with the Google Cloud Platform project resource you would like to connect to.

       Find this by navigating to the cloud console dashboard and selecting your project from the Select from drop-down. The project ID will be present in the Project info card.

     When you connect, the OAuth endpoint opens in your default browser. Log in and grant permissions to the application to completes the OAuth process. 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 Google Data Catalog JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.googledatacatalog.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.)
     

     Below is a typical connection string:

     jdbc:googledatacatalog:ProjectId=YourProjectId;InitiateOAuth=GETANDREFRESH;
     

   👁 Configuring the Data Server
   
4. On the Physical Schema screen, enter the following information:
   • Name: Select from the Drop Down menu.
   • Database (Catalog): Enter CData.
   • Owner (Schema): If you select a Schema for Google Data Catalog, enter the Schema selected, otherwise enter GoogleDataCatalog.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Google Data Catalog, enter the Schema selected, otherwise enter GoogleDataCatalog.
   👁 Configuring the Physical Schema
   
5. In the opened model click Reverse Engineer to retrieve the metadata for Google Data Catalog tables. 👁 Reverse Engineer the Model
   

Edit and Save Google Data Catalog Data

After reverse engineering you can now work with Google Data Catalog data in ODI. To view Google Data Catalog data, expand the Models accordion in the Designer navigator, right-click a table, and click View data. 👁 Viewing the data.

Create an ETL Project

Follow the steps below to create an ETL from Google Data Catalog. You will load Schemas entities into the sample data warehouse included in the ODI Getting Started VM.

1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

   Alternatively you can use SQLPlus. From a command prompt enter the following:

   sqlplus / as sysdba
   

2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the Schemas table in Google Data Catalog:

   CREATE TABLE ODI_DEMO.TRG_SCHEMAS (DATASETNAME NUMBER(20,0),Type VARCHAR2(255));
   

3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
4. Click Reverse Engineer. The TRG_SCHEMAS table is added to the model.
5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
6. Drag the TRG_SCHEMAS table from the Sales Administration model onto the mapping.
7. Drag the Schemas table from the Google Data Catalog model onto the mapping.
8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
9. Open the Physical tab of the Mapping Editor and click SCHEMAS_AP in TARGET_GROUP.
10. In the SCHEMAS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab. 👁 SQL-based access to Google Data Catalog enables you to use standard database-to-database knowledge modules.
    

You can then run the mapping to load Google Data Catalog data into Oracle.