[
https://issues.apache.org/jira/browse/HIVE-20776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666971#comment-16666971
]
Karthik Manamcheri commented on HIVE-20776:
-------------------------------------------
Should we then do the filtering both on client AND server side, instead of just
moving it?
{quote} HMS doesn't really know who the end-user is.
{quote}
HMS uses the hadoop proxy user system to know the end-user, no? This is how
Spark interacts with HMS. Spark sets the hadoop proxy user and HMS knows the
end-user through that. Why not use the same mechanism from HS2?
> Move HMS filterHooks from client-side to server-side
> ----------------------------------------------------
>
> Key: HIVE-20776
> URL: https://issues.apache.org/jira/browse/HIVE-20776
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Karthik Manamcheri
> Assignee: Karthik Manamcheri
> Priority: Major
>
> In HMS, I noticed that all the filter hooks are applied on the client side
> (in HiveMetaStoreClient.java). Is there any reason why we can't apply the
> filters on the server-side?
> Motivation: Some newer apache projects such as Kudu use HMS for metadata
> storage. Kudu is not completely Java-based and there are interaction points
> where they have C++ clients. In such cases, it would be ideal to have
> consistent behavior from HMS side as far as filters, etc are concerned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
