[SENTRY-1913] Incorrect constraints on AUTHZ_PATHS_MAPPING.AUTHZ_OBJ_NAME

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Assignee: Vamsee K. Yarlagadda
• Reporter: Alex Kolbasov
• Created: 01/Sep/17 19:31
• Updated: 05/Sep/17 05:14
• Resolved: 05/Sep/17 05:14

Description

SENTRY-1365 introduced the following constraint:

-- 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`);

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

Issue Links

• relates to: SENTRY-1365 Upgrading SQL script for HMSPaths persistence
• relates to: SENTRY-1805 Define a DB schema for HMS generation IDs
• links to: Review