[
https://issues.apache.org/jira/browse/ATLAS-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846217#comment-16846217
]
ASF subversion and git services commented on ATLAS-3080:
--------------------------------------------------------
Commit 045c0c07180f320223ccf60caf7249fbe6d824bf in atlas's branch
refs/heads/master from lina.li
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=045c0c0 ]
ATLAS-3080: Integration with Impala Hook API
Signed-off-by: Sarath Subramanian <[email protected]>
> 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
(v7.6.3#76005)
