![]() |
VOOZH | about |
Google Cloud Data Fusion simplifies building and managing data pipelines by offering a visual interface to connect, transform, and move data across various sources and destinations, streamlining data integration processes. When combined with CData Connect AI, it provides access to AlloyDB data for building and managing ELT/ETL data pipelines. This article explains how to use CData Connect AI to create a live connection to AlloyDB and how to connect and access live AlloyDB data from the Cloud Data Fusion platform.
Connectivity to AlloyDB from Cloud Data Fusion is made possible through CData Connect AI. To work with AlloyDB data from Cloud Data Fusion, we start by creating and configuring a AlloyDB connection.
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.
Find instructions about authentication setup on the AlloyDB Server here.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
The authentication with Kerberos is initiated by AlloyDB Server when the β is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.
π Configuring a connection (Salesforce is shown)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to AlloyDB data from Cloud Data Fusion.
Follow these steps to establish a connection from Cloud Data Fusion to AlloyDB through the CData Connect AI JDBC driver:
jdbc:connect:AuthScheme=Basic;user=username;password=PAT;
Please be aware that there is a known issue in Cloud Data Fusion where "int" types from source data are automatically cast as "long".
Now you have a direct connection to live AlloyDB data from from Google Cloud Data Fusion. You can create more connections to ensure a smooth movement of data across various sources and destinations, thereby streamlining data integration processes - all without replicating AlloyDB data.
To get real-time data access to hundreds of SaaS, Big Data, and NoSQL sources (including AlloyDB) directly from your cloud applications, explore the CData Connect AI.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial