[
https://issues.apache.org/jira/browse/SENTRY-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264292#comment-14264292
]
Hadoop QA commented on SENTRY-569:
----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12690034/SENTRY-569.001.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/241/console
This message is automatically generated.
> Workaround some operations for Authorization V2
> -----------------------------------------------
>
> Key: SENTRY-569
> URL: https://issues.apache.org/jira/browse/SENTRY-569
> Project: Sentry
> Issue Type: Sub-task
> Reporter: Xiaomeng Huang
> Assignee: Xiaomeng Huang
> Attachments: SENTRY-569.001.patch
>
>
> Currently V2 just get privilege hierarchy from entity, but now some
> operations don't have any ReadEnity and WriteEnity in Hive side(e.g.
> DROPTABLE). So add extend hierarchy from other way to make it workaround.
> In this jira, I implemented a simple semantic analyzer to extract db name and
> table name from command string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
