[RANGER-4193] ServiceTagsProcessor fails to handle update of an existing Service-Resource

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Ranger
• Assignee: Abhay Kulkarni
• Reporter: Abhay Kulkarni
• Created: 17/Apr/23 22:56
• Updated: 18/Apr/23 22:39
• Resolved: 18/Apr/23 22:39

Description

When an ENTITY_UPDATE notification is processed by tagsync process, it invokes Ranger admin's TagREST.importServiceTags() REST endpoint to add or update corresponding service-resource. However, if the incoming service-resource contains a GUID value, and Ranger admin's database does not have a service-resource that matches the GUID value, then instead of searching the database for the resource-signature, the implementation tries to create a service-resource. Such creation may fail with violation of uniqueness constraint for resource-signature value, resulting in the notification not correctly handled.

Issue Links

• is caused by: RANGER-3309 Support batch upload of tags to Ranger