![]() |
VOOZH | about |
The CData JDBC Driver for AlloyDB implements JDBC Standards and allows various applications, including Dremio, to work with live AlloyDB data. Dremio is a data lakehouse platform designed to empower self-service, interactive analytics on the data lake. With the CData JDBC driver, you can include live AlloyDB data as a part of your enterprise data lake. This article describes how to connect to AlloyDB data from Dremio as an External Source.
The CData JDBC Driver enables high-speed access to live AlloyDB data in Dremio. Once you install the driver, authenticate with AlloyDB and gain immediate access to AlloyDB data within your data lake. By surfacing AlloyDB data using native data types and handling complex filters, aggregations, & other operations automatically, the CData JDBC Driver grants seamless access to AlloyDB data.
This article assumes you are utilizing Docker to run Dremio. You can create a Docker container with the Dremio service using a command similar to the follow:
docker run -d --name dremio -p 9047:9047 -p 31010:31010 dremio/dremio-oss
Where dremio is the name of the container, 9047 is the container's port for the Dremio web interface and 31010 is the port that maps to the Dremio query service. dremio/dremio-oss specifies the image to use.
To use the CData JDBC Driver in Dremio, you need to build an Advanced Relation Pushdown (ARP) Connector. You can view the source code for the Connector on GitHub or download the ZIP file (GitHub.com) directly. Once you copy or extract the files, run the following command from the root directory of the connector (the directory containing the pom.xml file) to build the connector.
mvn clean install
NOTE: The CData ARP Connectors are build to be compiled with Java 11. Be sure to install Java 11 and use the correct version. You can update your Java version using a command similar to the following:
sudo update-alternatives --config java
Once the JAR file for the connector is built (in the target directory), you are ready to copy the ARP connector and JDBC Driver to your Dremio instance.
Install the ARP Connector to %DREMIO_HOME%/jars/ and the JDBC Driver for AlloyDB to %DREMIO_HOME%/jars/3rdparty. You can use commands similar to the following:
docker cp PATH\TO\dremio-alloydb-plugin-{DREMIO_VERSION}.jar dremio_image_name:/opt/dremio/jars/
docker cp PATH\TO\cdata.jdbc.alloydb.jar dremio_image_name:/opt/dremio/jars/3rdparty/
AlloyDB will now appear as an External Source option in Dremio. The ARP Connector built uses a JDBC URL to connect to AlloyDB data. The JDBC Driver has a built-in connection string designer that you can use (see below).
๐ External Sources via CData JDBC Drivers (Amazon DynamoDB & Couchbase are shown)For assistance in constructing the JDBC URL, use the connection string designer built into the AlloyDB JDBC Driver. Double-click the JAR file or execute the jar file from the command line.
java -jar cdata.jdbc.alloydb.jar
Fill in the connection properties and copy the connection string to the clipboard.
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.
๐ Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
NOTE: To use the JDBC Driver in Dremio, 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.
Add the Runtime Key (RTK) to the JDBC URL. You will end up with a JDBC URL similar to the following:
jdbc:alloydb:RTK=5246...;User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432
To add AlloyDB as an External Source, click to add a new source and select AlloyDB. Copy the JDBC URL and paste it into the New AlloyDB Source wizard.
๐ Entering the JDBC URL (Amazon DynamoDB is shown)Save the connection and you are ready to query live AlloyDB data in Dremio, easily incorporating AlloyDB data into your data lake.
๐ Live data in Dremio (Amazon DynamoDB is shown)Using the CData JDBC Driver for AlloyDB in Dremio, you can incorporate live AlloyDB data into your data lake. Check out our CData JDBC Driver for AlloyDB page for more information about connecting to AlloyDB. Download a free, 30 day trial of the CData JDBC Driver for AlloyDB and get started today.
Download a free trial of the AlloyDB Driver to get started:
Download NowLearn more:
๐ AlloyDB IconRapidly create and deploy powerful Java applications that integrate with AlloyDB.