[ 
https://issues.apache.org/jira/browse/RANGER-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhay Kulkarni updated RANGER-2313:
-----------------------------------
    Description: 
Tagsync fails to upload tags to Ranger admin if it is invoked using 
ranger-tagsync-upload.sh script in a secure cluster. This is a result of 
failure to establish kerberos identity in the described scenario.

Also, incorrect processing of ENTITY_CREATE and ENTITY_UPDATE notifications 
causes entities with no associated classifications to create corresponding 
Service Resource objects in Ranger Admin. Instead, such notifications should be 
dropped without further processing.

Atlas REST API to download tagged entities throttles the number of entities 
returned to 100 even when all entities are requested. Tagsync needs to call 
this API in a loop until no more entities are returned to ensure that all 
tagged entities are retrieved.



  was:Tagsync fails to upload tags to Ranger admin if it is invoked using 
ranger-tagsync-upload.sh script  in secure cluster. This is a result of failure 
to establish kerberos identity in the described scenario.


> tagsync fails to authenticate with ranger in kerberized cluster when using 
> ranger-tagsync-update.sh script
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-2313
>                 URL: https://issues.apache.org/jira/browse/RANGER-2313
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: master
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: master
>
>
> Tagsync fails to upload tags to Ranger admin if it is invoked using 
> ranger-tagsync-upload.sh script in a secure cluster. This is a result of 
> failure to establish kerberos identity in the described scenario.
> Also, incorrect processing of ENTITY_CREATE and ENTITY_UPDATE notifications 
> causes entities with no associated classifications to create corresponding 
> Service Resource objects in Ranger Admin. Instead, such notifications should 
> be dropped without further processing.
> Atlas REST API to download tagged entities throttles the number of entities 
> returned to 100 even when all entities are requested. Tagsync needs to call 
> this API in a loop until no more entities are returned to ensure that all 
> tagged entities are retrieved.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to