You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Arjun Mishra (JIRA)" <ji...@apache.org> on 2018/09/21 17:08:00 UTC

[jira] [Issue Comment Deleted] (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 ]

Arjun Mishra updated SENTRY-2406:
---------------------------------
    Comment: was deleted

(was: HashSet<List<DBModelAuthorizable>> doesn't remove duplicates. See image attached)

> 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
>         Attachments: SENTRY-2406.01.patch, SENTRY-2406.02.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
(v7.6.3#76005)