[
https://issues.apache.org/jira/browse/HIVE-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621823#comment-13621823
]
Prasad Mujumdar commented on HIVE-4232:
---------------------------------------
[~ashutoshc] thanks for the feedback.
Here are a couple of things to consider. Thrift SASL transport doesn't detect
if the other peer is not using the SASL transport
([THRIFT-1774|https://issues.apache.org/jira/browse/THRIFT-1774]). Hence if the
hiveserver and client are not using the same transport then the connection
simply hangs. Hence its using SASL transport as default and NOSASL is more of a
backdoor if you are using some non-java bindings that doesn't have thrift sasl
transport (and hence not listed in the hive-defaults).
IMO making non-sasl as default will lead to more problems than what it intends
to solve. For an end user , it doesn't matter what underlying authentication
libraries are used for the implementation. The normal authentication options
None, LDAP, Kerberos and Custom are self explanatory from point of view.
> 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
