[
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.
Approach should be similar to that of choosing authorization provider, where
the publication strategy can be chosen at runtime via configuration flag(s).
Scope of this ticket is to move lineage publication to the fe and add
appropriate hooks that a user can implement
was:
Impetus for this change is to allow lineage to be consumed by Altus via Kafka.
Approach should be similar to that of choosing authorization provider, where
the publication strategy can be chosen at runtime via configuration flag(s).
Scope of this ticket is to move lineage publication to the fe and add
appropriate hooks that a user can implement
> Refactor lineage publication mechanism to allow for different consumers
> -----------------------------------------------------------------------
>
> Key: IMPALA-8473
> URL: https://issues.apache.org/jira/browse/IMPALA-8473
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend, Frontend
> Reporter: radford nguyen
> Priority: Major
>
> Impetus for this change is to allow lineage to be consumed by Atlas via Kafka.
> Approach should be similar to that of choosing authorization provider, where
> the publication strategy can be chosen at runtime via configuration flag(s).
> Scope of this ticket is to move lineage publication to the fe and add
> appropriate hooks that a user can implement
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
