[
https://issues.apache.org/jira/browse/FLINK-31275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781841#comment-17781841
]
Zhenqiu Huang commented on FLINK-31275:
---------------------------------------
I am recently working Flink with open lineage integration. In our org,
customers mainly use the data stream api for icerberg, kafka, cassandra. As
table API is not even used, so implement these TableLineageVertex is probably
not the best way.
I feel the most painful thing is to infer the schema of source/source for
lineage perspective. If the schema info can be provided in Flink connector, the
integration in open lineage or even other framework will be clean, concise.
> Flink supports reporting and storage of source/sink tables relationship
> -----------------------------------------------------------------------
>
> Key: FLINK-31275
> URL: https://issues.apache.org/jira/browse/FLINK-31275
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.18.0
> Reporter: Fang Yong
> Assignee: Fang Yong
> Priority: Major
>
> FLIP-314 has been accepted
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-314%3A+Support+Customized+Job+Lineage+Listener
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
