sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-535) Optimize to reduce the call number of permsUpdate
Date Tue, 01 Dec 2015 00:30:10 GMT

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

Hadoop QA commented on SENTRY-535:
----------------------------------

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

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



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

This message is automatically generated.

> Optimize to reduce the call number of permsUpdate 
> --------------------------------------------------
>
>                 Key: SENTRY-535
>                 URL: https://issues.apache.org/jira/browse/SENTRY-535
>             Project: Sentry
>          Issue Type: Improvement
>            Reporter: Dapeng Sun
>            Assignee: Dapeng Sun
>            Priority: Minor
>         Attachments: SENTRY-535.patch, SENTRY-535.patch
>
>
> As the discussion in SENTRY-529, The {{SentryHDFSPlugin}} should not really care about
the column privileges. it should pick only the table level privileges and send it to the permsUpdate.



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

Mime
View raw message