[jira] Resolved: (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

["Sushanth Sowmyan (JIRA)" <ji...@apache.org>]

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

Sushanth Sowmyan resolved HIVE-1588.
------------------------------------

    Resolution: Invalid

Per discussion in the September Hive Dev Meetup, we'd decided to not follow the approach of having the client do filesystem operations, and introduce authentication/authorization and have the metastore server do the operations as the client user in HIVE-1476.

Thus, this jira is now not needed and can be closed.

> 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: 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.