[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fredy Wijaya updated IMPALA-8473:
-
Issue Type: Sub-task (was: Improvement)
Parent: IMPALA-8598
> Refactor lineage
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radford nguyen updated IMPALA-8473:
---
Description:
Impetus for this change is to allow lineage to be consumed by Atlas via Kafka.
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radford nguyen updated IMPALA-8473:
---
Description:
Impetus for this change is to allow lineage to be consumed by Atlas via Kafka.
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radford nguyen updated IMPALA-8473:
---
Description:
Impetus for this change is to allow lineage to be consumed by Atlas via Kafka.
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radford nguyen updated IMPALA-8473:
---
Attachment: ImpalaPostExecHook-infra.patch
> Refactor lineage publication mechanism to
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radford nguyen updated IMPALA-8473:
---
Description:
Impetus for this change is to allow lineage to be consumed by Atlas via Kafka.
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Garg updated IMPALA-8473:
Priority: Critical (was: Major)
> Refactor lineage publication mechanism to allow for different
[
https://issues.apache.org/jira/browse/IMPALA-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
radford nguyen updated IMPALA-8473:
---
Description:
Impetus for this change is to allow lineage to be consumed by Atlas via Kafka.
