[
https://issues.apache.org/jira/browse/HIVE-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621923#comment-13621923
]
Chris Drome commented on HIVE-4232:
-----------------------------------
[~prasadm][~cwsteinbach]: I think Prasad's point is fair. It explains why the
defaults were set the way they were and should probably be documented somewhere
in the code.
We have a follow-up patch which adds functionality to set the QOP of the
transport, so that data encryption can be enabled on the client-server
transport. This will require some changes to the JDBC connection string and I
wanted to get buy-in to modify the existing format of the connection string
before posting that patch.
I still feel the naming conventions are a little misleading and the JDBC
connection string tries to infer the state. However, if everyone agrees that
NOSASL should generally not be used, then I won't push that issue. Although it
doesn't help in the case a client library adds auth=nosasl, resulting in the
connection hanging.
> JDBC2 HiveConnection has odd defaults
> -------------------------------------
>
> Key: HIVE-4232
> URL: https://issues.apache.org/jira/browse/HIVE-4232
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, JDBC
> Affects Versions: 0.11.0
> Reporter: Chris Drome
> Assignee: Chris Drome
> Fix For: 0.11.0
>
> Attachments: HIVE-4232-1.patch, HIVE-4232.patch
>
>
> HiveConnection defaults to using a plain SASL transport if auth is not set.
> To get a raw transport auth must be set to noSasl; furthermore noSasl is case
> sensitive. Code tries to infer Kerberos or plain authentication based on the
> presence of principal. There is no provision for specifying QOP level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
