hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas Nair (Jira)" <>
Subject [jira] [Updated] (HIVE-20776) Run HMS filterHooks on server-side in addition to client-side
Date Wed, 20 Nov 2019 18:06:00 GMT


Thejas Nair updated HIVE-20776:
    Fix Version/s: 4.0.0
         Assignee: Na Li
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

Marking as resolved since this is committed to master

> Run HMS filterHooks on server-side in addition to client-side
> -------------------------------------------------------------
>                 Key: HIVE-20776
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Standalone Metastore
>            Reporter: Karthik Manamcheri
>            Assignee: Na Li
>            Priority: Major
>             Fix For: 4.0.0
>         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, HIVE-20776.009.patch, HIVE-20776.010.patch, HIVE-20776.011.patch, HIVE-20776.011.patch,
HIVE-20776.012.patch, HIVE-20776.013.patch, HIVE-20776.014.patch, HIVE-20776.015-branch-3.patch,
HIVE-20776.015.branch-3.patch, HIVE-20776.015.patch, HIVE-20776.015_a.branch-3.patch, HIVE-20776.016-branch-3.patch,
> In HMS, I noticed that all the filter hooks are applied on the client side (in
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

View raw message