Josh Rosen created SPARK-49650:
----------------------------------
Summary: Don't use deprecated Hive JDBC client parameters in docs
/ tests
Key: SPARK-49650
URL: https://issues.apache.org/jira/browse/SPARK-49650
Project: Spark
Issue Type: Improvement
Components: SQL
Affects Versions: 4.0.0
Reporter: Josh Rosen
Assignee: Josh Rosen
While looking at some hive-thriftserver unit tests logs, I saw spam like
{code:java}
20/06/05 06:35:55.442 pool-1-thread-1 WARN Utils: ***** JDBC param deprecation
*****
20/06/05 06:35:55.442 pool-1-thread-1 WARN Utils: The use of
hive.server2.transport.mode is deprecated.
20/06/05 06:35:55.442 pool-1-thread-1 WARN Utils: Please use transportMode like
so: jdbc:hive2://<host>:<port>/dbName;transportMode=<transport_mode_value>
20/06/05 06:35:55.442 pool-1-thread-1 WARN Utils: ***** JDBC param deprecation
*****
20/06/05 06:35:55.442 pool-1-thread-1 WARN Utils: The use of
hive.server2.thrift.http.path is deprecated.
20/06/05 06:35:55.442 pool-1-thread-1 WARN Utils: Please use httpPath like so:
jdbc:hive2://<host>:<port>/dbName;httpPath=<http_path_value> {code}
from deprecated JDBC connection string parameter usage.
It looks like we're using / recommending parameters that have been deprecated
for nearly a decade since https://issues.apache.org/jira/browse/HIVE-6972
We can clean these up to reduce some log spam for our tests (and our end users,
if we update the docs).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
