[
https://issues.apache.org/jira/browse/RANGER-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150546#comment-16150546
]
Nigel Jones commented on RANGER-1454:
-------------------------------------
The assumption in this Jira is that the existing Ranger REST API remains as it
is today. These changes to support new Atlas APIs are initially focussed only
at getting tagsync working properly with the new data model & approach to
classifications.
Once in place, since the Atlas Governance Engine OMAS api is consumer centric,
it is intended purely for enforcement engines such as ranger, and therefore the
Atlas can can extend as needed to improve integration with ranger. Better fine
grained notifications from atlas to ranger may also make it easier to update
policies more quickly, but would require other changes in ranger.
> Support of Atlas GAF OMAS
> --------------------------
>
> Key: RANGER-1454
> URL: https://issues.apache.org/jira/browse/RANGER-1454
> Project: Ranger
> Issue Type: New Feature
> Components: tagsync
> Reporter: Nigel Jones
> Assignee: Nigel Jones
> Labels: VirtualDataConnector
>
> A new v2 glossary capability is proposed for Atlas in ATLAS-1410.
> As part of this the glossary model becomes more sophisticated. In order to
> preserve the current simple tag(trait type):parms(trait instance)-entity
> relationship a new tagsync process will be developed that makes use of a new
> API proposed in ATLAS-1662. This would be an alternative to the current one
> so that existing users could continue unaffected, and a change is only
> required if moving to the v2 glossary implementation
> This will also allow the process of retrieving tags to be more efficient, and
> this new API can form a consumer-centric interface to support multiple
> enforcement technologies, including, but not restricted to, Ranger.
> feel free to assign to me/modify permissions ;-)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
