[
https://issues.apache.org/jira/browse/ATLAS-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810321#comment-16810321
]
Dinesh Garg commented on ATLAS-3080:
------------------------------------
Per our discussion toda,y I assume this wont be a blocker anymore. This is a
requirement for the long term not for CDP 1.0
For CDP 1.0, we are going to explore the option of making the DDL operation
info available in Lineage file. Some tool in Atlas will pick it from there and
put it in Kafka.
> Impala should send notification for DDL operation to Atlas through Kafka
> ------------------------------------------------------------------------
>
> 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
> Priority: Blocker
>
> 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)
