[RANGER-1820] Duplicate entries should be deleted before creation of unique index on x_group and x_group_users table

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0, 0.6.0, 0.7.0, 1.0.0
• Fix Version/s: 1.0.0, 0.7.2
• Component/s: Ranger
• Assignee: Pradeep Agrawal
• Reporter: Pradeep Agrawal
• Created: 30/Sep/17 11:44
• Updated: 18/Oct/17 19:07
• Resolved: 18/Oct/17 19:07

Description

Currently, concurrent request to create a group and group-users mapping is causing duplicate entries of the same group in the x_group table and user-group mapping entry in the x_group_users table. Duplicate entry creation has been restricted through the RANGER-1765 patch which creates unique constraints on the x_group and x_group_users table. But unique index creation may fail if there is already duplicate entries(likely to happen in upgrade case) so we should delete duplicate entries of these tables before creating the unique index. If the reference of duplicate group id is being used in child table then the id of the duplicate group shall be updated in the child table. In case of duplicate entries of the same group name; group name having the minimum id(created first) shall be given higher preference and will not be deleted from the x_group table.

Issue Links

• is related to: RANGER-1765 Add unique key constraint in x_group and x_group_users table
• links to: Review Request Link-1
• links to: Review Request Link-2