[
https://issues.apache.org/jira/browse/HIVE-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551026#comment-14551026
]
Thejas M Nair commented on HIVE-10753:
--------------------------------------
Several non hive config parameters can also be set through the url. This
includes tez/mr parameters. This check will disallow that.
There are two issues here.
1. It is hard for the user to figure out why the connection attempt failed. I
think we can do something simple like printing the transport mode and other
settings for connection that are getting used (transport mode, sasl, ssl ).
2. The failure is an OOM. Is it possible to not OOM and probably given an error
about wrong transport mode ?
These two issues can be talked as part of different jiras if necessary.
> hs2 jdbc url - wrong connection string cause OOM error on beeline/jdbc/odbc
> client, misleading message
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-10753
> URL: https://issues.apache.org/jira/browse/HIVE-10753
> Project: Hive
> Issue Type: Bug
> Components: Beeline, JDBC
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-10753.1.patch
>
>
> {noformat}
> beeline -u
> 'jdbc:hive2://localhost:10001/default?httpPath=/;transportMode=http' -n
> hdiuser
> scan complete in 15ms
> Connecting to
> jdbc:hive2://localhost:10001/default?httpPath=/;transportMode=http
> Java heap space
> Beeline version 0.14.0.2.2.4.1-1 by Apache Hive
> 0: jdbc:hive2://localhost:10001/default (closed)> ^Chdiuser@headnode0:~$
> But it works if I use the deprecated param -
> hdiuser@headnode0:~$ beeline -u
> 'jdbc:hive2://localhost:10001/default?hive.server2.transport.mode=http;httpPath=/'
> -n hdiuser
> scan complete in 12ms
> Connecting to
> jdbc:hive2://localhost:10001/default?hive.server2.transport.mode=http;httpPath=/
> 15/04/28 23:16:46 [main]: WARN jdbc.Utils: ***** JDBC param deprecation *****
> 15/04/28 23:16:46 [main]: WARN jdbc.Utils: The use of
> hive.server2.transport.mode is deprecated.
> 15/04/28 23:16:46 [main]: WARN jdbc.Utils: Please use transportMode like so:
> jdbc:hive2://<host>:<port>/dbName;transportMode=<transport_mode_value>
> Connected to: Apache Hive (version 0.14.0.2.2.4.1-1)
> Driver: Hive JDBC (version 0.14.0.2.2.4.1-1)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 0.14.0.2.2.4.1-1 by Apache Hive
> 0: jdbc:hive2://localhost:10001/default> show tables;
> +------------------+--+
> | tab_name |
> +------------------+--+
> | hivesampletable |
> +------------------+--+
> 1 row selected (18.181 seconds)
> 0: jdbc:hive2://localhost:10001/default> ^Chdiuser@headnode0:~$ ^C
> {noformat}
> The reason for the above message is :
> The url is wrong. Correct one:
> {code}
> beeline -u
> 'jdbc:hive2://localhost:10001/default;httpPath=/;transportMode=http' -n
> hdiuser
> {code}
> Note the ";" instead of "?". The deprecation msg prints the format as well:
> {code}
> Please use transportMode like so:
> jdbc:hive2://<host>:<port>/dbName;transportMode=<transport_mode_value>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
