[
https://issues.apache.org/jira/browse/RANGER-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036957#comment-16036957
]
Nigel Jones commented on RANGER-1454:
-------------------------------------
correct, thanks for spotting. the ATLAS-1662 I referred to does refer to the
governance action OMAS, but the abstract of this Jira is badly named. It is to
support the new glossary implementation in Atlas, but that is exposed to ranger
through the governanance action OMAS. I'll update the title.
> Support of Atlas v2 glossary API proposal for tag source
> --------------------------------------------------------
>
> 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.3.15#6346)
