[
https://issues.apache.org/jira/browse/SENTRY-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150040#comment-15150040
]
Hadoop QA commented on SENTRY-1066:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12788176/SENTRY-1066.1.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/1212/console
This message is automatically generated.
> Sentry oracle upgrade script failed with ORA-0955 duplicate name issue
> ----------------------------------------------------------------------
>
> Key: SENTRY-1066
> URL: https://issues.apache.org/jira/browse/SENTRY-1066
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.5.1, 1.7.0
> Reporter: Anne Yu
> Assignee: Anne Yu
> Priority: Blocker
> Attachments: SENTRY-1066.0.patch, SENTRY-1066.1.patch
>
>
> We've seen ORA-0955 duplicate name issue while running Sentry upgrade scripts.
> Running Oracle 11g. We eventually tracked it to
> /opt/cloudera/parcels/CDH/lib/sentry/scripts/sentrystore/upgrade/004-SENTRY-74.oracle.sql:
> {code:sql}
> ALTER TABLE SENTRY_DB_PRIVILEGE DROP CONSTRAINT
> "SENTRY_DB_PRIV_PRIV_NAME_UNIQ";
> ALTER TABLE SENTRY_DB_PRIVILEGE ADD CONSTRAINT
> "SENTRY_DB_PRIV_PRIV_NAME_UNIQ" UNIQUE
> ("SERVER_NAME","DB_NAME","TABLE_NAME","COLUMN_NAME","URI","ACTION","WITH_GRANT_OPTION");
> {code}
> Although constraint was dropped, it fails to re-add, as there was an implicit
> index added with same name as well (expected behavior according to docs:
> http://docs.oracle.com/cd/B19306_01/server.102/b14200/clauses002.htm See:
> "Unique Constraints").
> Dropping the index allowed us to finish upgrading the schema successfully.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
