You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/09/01 08:33:00 UTC

[jira] [Commented] (RANGER-1670) Change in Atlas Kafka consumer interface for Atlas tag sync.

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

Nigel Jones commented on RANGER-1670:
-------------------------------------

Hi,
 I thought it worth mentioning that beyond the just-being-released 0.8.1, there's a fair bit of work going in with Atlas currently, to enrichen the data model, and to provide new consumer centric interfaces. The glossary is being expanded a lot, to enhance the relationships between assets, business terms & classifications. The idea is to surface a more consumer centric view of this for ranger (and other enforcement engines). In RANGER-1454 I propose to switch to using this new API, but it's fair to say the focus so far has been on the atlas side, and it's only now we're getting more into the ranger aspects (thinking of....!), which was a little tricky before the atlas side started firming up.

I'd love your feedback on the ideas and happy to chat more. 

> Change in Atlas Kafka consumer interface for Atlas tag sync.
> ------------------------------------------------------------
>
>                 Key: RANGER-1670
>                 URL: https://issues.apache.org/jira/browse/RANGER-1670
>             Project: Ranger
>          Issue Type: Bug
>          Components: tagsync
>            Reporter: Nixon Rodrigues
>         Attachments: RANGER-1670.patch
>
>
> This change is dependent on upcoming 0.8.1 Atlas release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)