[
https://issues.apache.org/jira/browse/SENTRY-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151371#comment-16151371
]
Hadoop QA commented on SENTRY-1913:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12885030/SENTRY-1913.01-master.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/3222/console
This message is automatically generated.
> Incorrect constraints on AUTHZ_PATHS_MAPPING.AUTHZ_OBJ_NAME
> -----------------------------------------------------------
>
> Key: SENTRY-1913
> URL: https://issues.apache.org/jira/browse/SENTRY-1913
> Project: Sentry
> Issue Type: Bug
> Reporter: Alexander Kolbasov
> Assignee: Vamsee Yarlagadda
> Priority: Blocker
> Attachments: SENTRY-1913.01-master.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> SENTRY-1365 introduced the following constraint:
> {code}
> -- Constraints for table `AUTHZ_PATHS_MAPPING` for class(es)
> [org.apache.sentry.provider.db.service.model.MAuthzPathsMapping]
> CREATE UNIQUE INDEX `AUTHZOBJNAME` ON `AUTHZ_PATHS_MAPPING`
> (`AUTHZ_OBJ_NAME`);
> {code}
> Later (SENTRY-1805) we added snapshot generation (AUTHZ_SNAPSHOT_ID). What
> should be unique is the combination. of object name and snapshot ID.
> Here, for some reason HMSFollower decided to create a new full snapshot while
> there was one present. And it couldn't do that because of the duplicate entry
> - it couldn't write the same object with a different ID.
> Sop we should change the UNIQUE to be on two fields
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
