You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Nikhil Purbhe (JIRA)" <ji...@apache.org> on 2018/02/14 10:22:00 UTC

[jira] [Assigned] (RANGER-1897) TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient tag-download from Atlas

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

Nikhil Purbhe reassigned RANGER-1897:
-------------------------------------

    Assignee: Nikhil Purbhe  (was: Madhan Neethiraj)

> TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient tag-download from Atlas
> ----------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1897
>                 URL: https://issues.apache.org/jira/browse/RANGER-1897
>             Project: Ranger
>          Issue Type: Bug
>          Components: tagsync
>    Affects Versions: 0.7.2
>            Reporter: Madhan Neethiraj
>            Assignee: Nikhil Purbhe
>            Priority: Major
>             Fix For: 1.0.0, 0.7.2
>
>         Attachments: RANGER-1897.patch
>
>
> Currently tag-synchronization via REST API method uses Atlas V1 APIs, which requires large number of calls from Ranger tag-sync to Atlas server. In environments having large number of entities, this approach can take a long time to download tags from Atlas. Use of Atlas V2 APIs would significantly improve the performance.



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