You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Kalyan Kalvagadda (Jira)" <ji...@apache.org> on 2020/01/02 17:08:04 UTC

[jira] [Updated] (SENTRY-2406) Make sure inputHierarchy and outputHierarchy have unique values

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

Kalyan Kalvagadda updated SENTRY-2406:
--------------------------------------
    Fix Version/s: 2.2.0

> Make sure inputHierarchy and outputHierarchy have unique values
> ---------------------------------------------------------------
>
>                 Key: SENTRY-2406
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2406
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.1.0
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Major
>             Fix For: 2.2.0
>
>         Attachments: SENTRY-2406.01.patch, SENTRY-2406.02.patch, SENTRY-2406.03.patch
>
>
> When building input or output hierarchy list, we iterate over all ReadEntity inputs received from Hive. The inputs particularly have accessed columns that can repeat for other ReadEntity objects. This happens definitively when a table has partitions. We should in general protect Sentry from not having to authorize over a list of DBModelAuthorizable objects when it has already been done. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)