[jira] [Commented] (RANGER-1454) Support of Atlas v2 glossary API proposal for tag source

["Nigel Jones (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RANGER-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005066#comment-16005066 ] 

Nigel Jones commented on RANGER-1454:
-------------------------------------

Yes I've raised this as a placeholder for now. Once the glossary itself becomes clearer, then I believe we should have a new API on Atlas which exposes the tags in a ranger-friendly form (also the subject of a related jira). 
The v2 glossary is more sophisticated so there are multiple levels of classifications .. but the new API (pointed to by a new tagsync, or a variant thereof)  can allow ranger to work the same as today. The discussion after that may be to consider whether any additional metadata should be available in ranger as a first-class entity so that it can easily be used in rules... but we're a fair few steps away from that ;-)

> 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)