hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Crawford (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2767) Optionally use framed transport with metastore
Date Mon, 27 Feb 2012 23:39:48 GMT

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

Travis Crawford commented on HIVE-2767:
---------------------------------------

Thanks for the feedback Ashutosh - if this is something you'd consider adding I can update
based on current trunk if things have changed.

While there may be perf gains, this is needed to integrate with our compute grid. Basically
a wrapper registers the metastore host:port in zookeeper, and a thrift framed-transport-only
proxy proxies metastore requests based on its ZK registration. This lets us launch the metastore
on our mesos cluster and still give clients the hard-coded host:port they expect.
                
> 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

        

Mime
View raw message