You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2019/01/04 16:08:00 UTC

[jira] [Updated] (HIVE-20776) Run HMS filterHooks on server-side in addition to client-side

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

Na Li updated HIVE-20776:
-------------------------
    Attachment: HIVE-20776.009.patch

> Run HMS filterHooks on server-side in addition to client-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: Na Li
>            Priority: Major
>         Attachments: HIVE-20776.001.patch, HIVE-20776.003.patch, HIVE-20776.004.patch, HIVE-20776.005.patch, HIVE-20776.006.patch, HIVE-20776.007.patch, HIVE-20776.007.patch, HIVE-20776.008.patch, HIVE-20776.009.patch
>
>
> 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)