JingsongLi commented on code in PR #8476: URL: https://github.com/apache/paimon/pull/8476#discussion_r3527365129
########## docs/docs/flink/lineage.md: ########## @@ -0,0 +1,32 @@ +--- +title: "Data Lineage" +sidebar_position: 13 +--- + +# Data Lineage + +Paimon implements [FLIP-314](https://cwiki.apache.org/confluence/spaces/FLINK/pages/240884116/FLIP-294+Support+Customized+Catalog+Modification+Listener) to expose lineage information through Flink's native `LineageVertexProvider` interface. This allows lineage consumers (such as [OpenLineage](https://openlineage.io/docs/integrations/flink/flink2)) to automatically discover Paimon datasets in the Flink job graph. Review Comment: This link currently points to FLIP-294 (the catalog modification listener), while the text says FLIP-314. Could we point it to the actual FLIP-314 job lineage listener page so readers land on the lineage proposal instead of a different FLIP? ########## docs/docs/flink/lineage.md: ########## @@ -0,0 +1,32 @@ +--- +title: "Data Lineage" +sidebar_position: 13 +--- + +# Data Lineage + +Paimon implements [FLIP-314](https://cwiki.apache.org/confluence/spaces/FLINK/pages/240884116/FLIP-294+Support+Customized+Catalog+Modification+Listener) to expose lineage information through Flink's native `LineageVertexProvider` interface. This allows lineage consumers (such as [OpenLineage](https://openlineage.io/docs/integrations/flink/flink2)) to automatically discover Paimon datasets in the Flink job graph. + +## Table API / SQL + +When using Paimon tables via Flink SQL or Table API, lineage is automatically reported for both source and sink tables. Review Comment: This reads as unconditional, but the note below says the Flink planner change needed to extract Paimon datasets from DataStreamScanProvider/DataStreamSinkProvider is still pending. Could we scope this to Flink versions that contain that upstream change, or phrase Table API/SQL lineage as partial until that PR is merged and released? Otherwise users may configure the listener and still get events missing the Paimon datasets. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
