Zoltán Borók-Nagy created IMPALA-10571:
------------------------------------------
Summary: ImpalaJdbcClient might silently choose a different driver
than the one specified
Key: IMPALA-10571
URL: https://issues.apache.org/jira/browse/IMPALA-10571
Project: IMPALA
Issue Type: Bug
Reporter: Zoltán Borók-Nagy
I was experimenting with drivers while running into this issue.
I tried to do some testing with a custom JDBC driver with the following command:
{noformat}
bin/run-jdbc-client.sh -d "my.impala.jdbc.Driver" -t NOSASL -q "select
1"{noformat}
The script outputted:
{noformat}
Using JDBC Driver Name: my.impala.jdbc.Driver
Connecting to: jdbc:impala://localhost:21050
Executing: select sleep(12000)
----[START]----
1
----[END]----{noformat}
However, after some debugging I figured out that ImpalaJdbcClient actually used
org.apache.hive.jdbc.HiveDriver. It was because the specified driver didn't
accept the default connection string (jdbc:hive2://...), therefore the
HiveDriver was being used.
I think instead of silently choosing a different driver, ImpalaJdbcClient
should raise an error and tell the user to specify the connection string as
well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
