hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Commented) (JIRA)" <>
Subject [jira] [Commented] (HIVE-2767) Optionally use framed transport with metastore
Date Sat, 07 Apr 2012 17:52:17 GMT


Phabricator commented on HIVE-2767:

ashutoshc has requested changes to the revision "HIVE-2767 [jira] Optionally use framed transport
with metastore".

  What will happen if the config variable is set to true in client, but is false in server
and vice-versa?

  common/src/java/org/apache/hadoop/hive/conf/ This also needs to be added
in conf/hive-default.xml.template which serve as a documentation.
  metastore/src/java/org/apache/hadoop/hive/metastore/ In your earlier
version of patch you were throwing exception in case both secure mode as well as framed transport
is set to true. If you have tested with both true and it works then its fine, otherwise we
should throw an exception here.



> Optionally use framed transport with metastore
> ----------------------------------------------
>                 Key: HIVE-2767
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: HIVE-2767.D2661.1.patch, HIVE-2767.patch.txt, HIVE-2767_a.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:!default.jspa
For more information on JIRA, see:


View raw message