[
https://issues.apache.org/jira/browse/RANGER-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-4193:
-------------------------------------
Fix Version/s: 3.0.0
2.5.0
> 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
> Priority: Major
> Fix For: 3.0.0, 2.5.0
>
>
> 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)
