You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Abhay Kulkarni (Jira)" <ji...@apache.org> on 2023/04/17 22:57:00 UTC

[jira] [Created] (RANGER-4193) ServiceTagsProcessor fails to handle update of an existing Service-Resource

Abhay Kulkarni created RANGER-4193:
--------------------------------------

             Summary: ServiceTagsProcessor fails to handle update of an existing Service-Resource
                 Key: RANGER-4193
                 URL: https://issues.apache.org/jira/browse/RANGER-4193
             Project: Ranger
          Issue Type: Bug
          Components: Ranger
            Reporter: Abhay Kulkarni
            Assignee: Abhay Kulkarni


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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)