[
https://issues.apache.org/jira/browse/FLINK-36410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenqiu Huang updated FLINK-36410:
----------------------------------
Description: We find that lineage interface adoption is not easy for each
of Flink connectors as every connect has its own release dependency and
schedule. Thus, to make the lineage integration incrementally used by user, we
want to change the lineage info collection not require both source and sink as
lineage provider implemented. So that Lineage reporter can has partial lineage
graph generated.
> Improve Lineage Info Collection for flink app
> ---------------------------------------------
>
> Key: FLINK-36410
> URL: https://issues.apache.org/jira/browse/FLINK-36410
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Runtime
> Affects Versions: 1.20.0
> Reporter: Zhenqiu Huang
> Priority: Minor
>
> We find that lineage interface adoption is not easy for each of Flink
> connectors as every connect has its own release dependency and schedule.
> Thus, to make the lineage integration incrementally used by user, we want to
> change the lineage info collection not require both source and sink as
> lineage provider implemented. So that Lineage reporter can has partial
> lineage graph generated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
