hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1588) Allowing Hive's metastore when it runs as a thrift service to run as a pure metadata service and not perform any filesystem operations
Date Tue, 24 Aug 2010 18:59:24 GMT

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

Sushanth Sowmyan commented on HIVE-1588:
----------------------------------------

An additional motivation behind this approach as opposed to simply renewing tokens would be
that you also only perform filesystem read operations as the same user that performs write
operations(i.e. both on client side)

> Allowing Hive's metastore when it runs as a thrift service to run as a pure metadata
service and not perform any filesystem operations
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-1588
>                 URL: https://issues.apache.org/jira/browse/HIVE-1588
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Sushanth Sowmyan
>
> To integrate with Secure Hadoop, filesystem accesses would require an auth token, which
has an expiry. Thus, if we were running hive with a thrift metastore server, the server process
would need to frequently renew tokens.
> One potential way of dealing with that is to have the metastore server be a pure metadata
service, and not perform any filesystem operations, which is taking the approach HIVE-1476
takes a step further, extending it for reads as well as writes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message