hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mithun Radhakrishnan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4232) JDBC2 HiveConnection has odd defaults
Date Mon, 08 Apr 2013 17:15:16 GMT

    [ https://issues.apache.org/jira/browse/HIVE-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625557#comment-13625557
] 

Mithun Radhakrishnan commented on HIVE-4232:
--------------------------------------------

Hello, [~cwsteinbach]. Hi, [~prasadm]. 

Could you please help us understand the rationale behind the choice of default (plainsasl,
i.e. erstwhile NONE)? I mean, before the Thrift-hang. The manner in which the auth-protocol
is deduced is far from intuitive.

The Thrift-1774 bug is an unfortunate aside that one wishes could be resolved in Thrift. While
I concede HiveServer2 has been in trunk for a while (and might well have customers using it),
it's not been in an official Hive release prior to 0.11. Surely, now (i.e. before 0.11 release)
is the opportune moment to change the defaults and fix the format of the jdbc-connect-string?

[~cdrome] does make a valid point about the client needing to be in sync with the server's
auth method anyway.

                
> 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

Mime
View raw message