ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikhil Purbhe (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (RANGER-1897) TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient tag-download from Atlas
Date Wed, 14 Feb 2018 10:22:00 GMT

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

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

    Assignee: Madhan Neethiraj  (was: Nikhil Purbhe)

> 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: Madhan Neethiraj
>            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)

Mime
View raw message