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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENTRY-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622871#comment-16622871 ] 

Hadoop QA commented on SENTRY-2406:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12940654/SENTRY-2406.01.patch against master.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/4137/console

This message is automatically generated.

> 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
>
>
> 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)