Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 177DD104B5 for ; Wed, 25 Sep 2013 19:12:19 +0000 (UTC) Received: (qmail 34071 invoked by uid 500); 25 Sep 2013 19:12:10 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 33710 invoked by uid 500); 25 Sep 2013 19:12:08 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 33502 invoked by uid 500); 25 Sep 2013 19:12:07 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 33326 invoked by uid 99); 25 Sep 2013 19:12:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 19:12:05 +0000 Date: Wed, 25 Sep 2013 19:12:05 +0000 (UTC) From: "Vaibhav Gumashta (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-4232) JDBC2 HiveConnection has odd defaults MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777938#comment-13777938 ] Vaibhav Gumashta commented on HIVE-4232: ---------------------------------------- Hi [~prasadm], possible to take a look at this again? I feel the way auth parameters are passed in JDBC uri is quite confusing and not very clean. NONE/NOSASL is also misleading and exposes a risk of misinterpretation while developing, which will compound as more stuff is built on this. My proposal (similar to [~thejas]): 1. Have all comparison case insensitive. 2. While parsing the uri in Utils#parseURL, set the auth config parameter for each mode. When it is not specified, set it to the default of PLAINSASL. This cleans HiveConnection#openTransport. 3. hive.server2.authentication=NOSASL -> Raw transport -> jdbc:hive2://host:port/dbname;auth=nosasl 4. hive.server2.authentication=PLAINSASL -> Plain SASL transport -> jdbc:hive2://host:port/dbname;auth=plainsasl(or no-auth specified) 5. hive.server2.authentication=KERBEROS -> Kerberos SASL transport -> jdbc:hive2://host:port/dbname;auth=kerberos;principal=;qop= > 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, 0.12.0 > Reporter: Chris Drome > Assignee: Chris Drome > Attachments: HIVE-4232-1.patch, HIVE-4232-2.patch, HIVE-4232-3-0.11.patch, HIVE-4232-3-trunk.patch, HIVE-4232-4-0.11.patch, HIVE-4232-4-trunk.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