You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Lenni Kuff (JIRA)" <ji...@apache.org> on 2015/11/25 07:19:11 UTC

[jira] [Updated] (SENTRY-565) Improve performance of filtering Hive SHOW commands

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

Lenni Kuff updated SENTRY-565:
------------------------------
    Summary: Improve performance of filtering Hive SHOW commands  (was: Improvement the performance when Sentry filter the entity)

> Improve performance of filtering Hive SHOW commands
> ---------------------------------------------------
>
>                 Key: SENTRY-565
>                 URL: https://issues.apache.org/jira/browse/SENTRY-565
>             Project: Sentry
>          Issue Type: Improvement
>            Reporter: Colin Ma
>            Assignee: Colin Ma
>             Fix For: 1.7.0
>
>         Attachments: SENTRY-565.001.patch, SENTRY-565.002.patch, SENTRY-565.003.patch, SENTRY-565.004.patch, SENTRY-565.005.patch, SENTRY-565.006.patch, SENTRY-565.007.patch
>
>
> Currently, when get the metadata from hive, eg, "show tables", "show databases". Sentry will filter the result and output the authorized entities. There will be many RPC calls when filtering the result. The related code is in HiveAuthzBinding, for example, in filterShowTables:
> {code}
> ......
> for (String tableName : queryResult) {
>   ......
>   hiveAuthzBinding.authorize(operation, tableMetaDataPrivilege, subject, inputHierarchy,
>             outputHierarchy, providedPrivileges);
>   ......
> }
> ......
> {code}
> hiveAuthzBinding.authorize will get the privileges from sentry service, if there are many tables in the hive, the filtering process will spend much time. Considering sentry also need to filter the column, HiveAuthzBinding should be improved to reduce the number of rpc calls when doing the filter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)