[
https://issues.apache.org/jira/browse/SENTRY-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038034#comment-14038034
]
SentryQA commented on SENTRY-162:
---------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12651509/SENTRY-162.4.patch
against master.
{color:red}Overall:{color} -1 due to 3 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-SENTRY-Build/176/console
This message is automatically generated.
> Cleanup DB store privilege metadata on Hive DDL statements
> ----------------------------------------------------------
>
> Key: SENTRY-162
> URL: https://issues.apache.org/jira/browse/SENTRY-162
> Project: Sentry
> Issue Type: Bug
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Labels: grant/revoke
> Attachments: SENTRY-162-noThrift.1.patch,
> SENTRY-162-noThrift.2.patch, SENTRY-162.1.patch, SENTRY-162.2.patch,
> SENTRY-162.4.patch
>
>
> The hive statements like drop table, alter table rename etc will rename or
> destroy the DB objects. We need to update the privilege metadata for these
> objects the accordingly.
> At minimum, we need to handle it for following -
> DROP TABLE
> DROP DATABASE
> ALTER TABLE RENAME
--
This message was sent by Atlassian JIRA
(v6.2#6252)