You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "radford nguyen (JIRA)" <ji...@apache.org> on 2019/04/30 18:59:00 UTC
[jira] [Created] (IMPALA-8473) Refactor lineage publication
mechanism to allow for different consumers
radford nguyen created IMPALA-8473:
--------------------------------------
Summary: 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
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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org