You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "haidong chen (Jira)" <ji...@apache.org> on 2020/03/30 10:12:00 UTC

[jira] [Commented] (ATLAS-3080) Integration with Impala Hook API

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

haidong chen commented on ATLAS-3080:
-------------------------------------

hi guys, I am a new user who is currently integration impala with atlas, is it possible anyone can walk me through the process of the integration impala with atlas?? 

> Integration with Impala Hook API
> --------------------------------
>
>                 Key: ATLAS-3080
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3080
>             Project: Atlas
>          Issue Type: Task
>          Components: atlas-intg
>    Affects Versions: 1.1.0
>            Reporter: Na Li
>            Assignee: Na Li
>            Priority: Blocker
>         Attachments: ATLAS-3080.013.patch
>
>
> This jira focuses on integration with Impala hook API. 
> if user needs Tag based security policy for tables in Impala, we need the table metadata in Atlas, like assigning a PII tag for an Impala table in atlas and enforce security policy in Ranger for the tag ‘PII’ on who can access/modify it.
> Atlas does not allow user to configure tag on a table if Atlas has not received notification about that table creation. Right now, Impala does not send notifications for DDL operation. Therefore, we need to add Atlas code to integrate with Impala.
> Besides this use case, sending notifications to Atlas allow other functionalities to consume Impala DDL operation activities.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)