如何在 JDBC Sink Connector 中配置 hive-jdbc-uber-jar

Question

I'm trying to use hive-jdbc-uber-jar and configure the JDBC sink connector.

But the connector is throwing error:

[2022-08-31 00:21:21,583] INFO Unable to connect to database on attempt 1/3. Will retry in 10000 ms. (io.confluent.connect.jdbc.util.CachedConnectionProvider)
java.sql.SQLException: **No suitable driver** found for **jdbc:hive2**://XX.XX.XX.XX:10002/test;auth=noSasl;transportMode=http;httpPath=cliservice

Config

    {
      "name": "connector_schema_test_v01",
      "config": {
        "value.converter.schema.registry.url": "http://schema-registry:8081",
        "key.converter.schema.registry.url": "http://schema-registry:8081",
        "name": "connector_schema_test_v01",
        "connector.class": "io.confluent.connect.jdbc.JdbcSinkConnector",
        "tasks.max": "1",
        "key.converter": "io.confluent.connect.avro.AvroConverter",
        "value.converter": "io.confluent.connect.avro.AvroConverter",
        "topics": "topic_schema_test_v05",
        "connection.url": "jdbc:hive2://XX.XX.XX.XX:10002/test;auth=noSasl;transportMode=http;httpPath=cliservice",
        "connection.user": "",
        "connection.password": "",
        "insert.mode": "upsert",
        "delete.enabled": "true",
        "table.name.format": "delta_try_v1_2",
        "pk.mode": "record_key",
        "pk.fields": "K1, K2",
        "auto.create": "true",
        "auto.evolve": "true"
      }
    }

The driver is in the path: /usr/share/confluent-hub-components/confluentinc-kafka-connect-jdbc/lib

I have restart the connector, but same error. I think driver class name has to be set in some property.

The driver and the URL are working in a SQL editor

Any idea?

Answer 1

The hive-jdbc-uber-jar project was created in 2014 and now comes with this warning:

When I first created this project in 2014 the Hive project did not produce a "standalone" jar that reliably contained all required dependencies to successfully create a JDBC connection. Since that time the community has resolved many, if not all, of those early issues. As of today, the "standalone" jar published by recent versions of Hive make this project mostly obsolete. You can grab the official Hive standalone jar using maven.

Perhaps you can just use Hive as follows and that will solve your issue:

<dependency>
    <groupId>org.apache.hive</groupId>
    <artifactId>hive-jdbc</artifactId>
    <version>YOUR VERSION OF HIVE</version>
    <classifier>standalone</classifier>
</dependency>