Alexander Kolbasov created SENTRY-1913:
------------------------------------------
Summary: 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
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)
