Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 27 Feb 2012 23:01:50 +0000 (UTC)
From: "Ashutosh Chauhan (Assigned) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <272281209.25312.1330383710591.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <106400242.12202.1328032811755.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HIVE-2767) Optionally use framed transport with
 metastore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashutosh Chauhan reassigned HIVE-2767:
--------------------------------------

    Assignee: Travis Crawford

Patch looks ok to me. I presume this is for performance. Just curious, have you seen substantial performance gains because of this. Since, most of the rpc call in MetaStore are of fairly small payload. To me, it appears it won't bring in much perf gains.
                
> Optionally use framed transport with metastore
> ----------------------------------------------
>
>                 Key: HIVE-2767
>                 URL: https://issues.apache.org/jira/browse/HIVE-2767
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: HIVE-2767.patch.txt
>
>
> Users may want/need to use thrift's framed transport when communicating with the Hive MetaStore. This patch adds a new property {{hive.metastore.thrift.framed.transport.enabled}} that enables the framed transport (defaults to off, aka no change from before the patch). This property must be set for both clients and the HMS server.
> It wasn't immediately clear how to use the framed transport with SASL, so as written an exception is thrown if you try starting the server with both options. If SASL and the framed transport will indeed work together I can update the patch (although I don't have a secured environment to test in).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira