šš§š-ššØ-šš§š šššš šš¢š§ššš š š°š¢šš” šššš¤š, š
š„š¢š§š¤, šš©šš«š¤, šš§š šššššš«š š®š¬š¢š§š šš©šš§šš¢š§ššš š
I've created a complete, hands-on tutorial that shows how to capture and visualize data lineage from the source all the way through to downstream analytics. The project follows data from a single Apache Kafka topic as it branches into multiple parallel pipelines, with the entire journey visualized in ššš«šŖš®šš³.
The guide walks through a modern, production-style stack:
ā
šš©ššš”š šššš¤š - Using Kafka Connect with a custom šš©šš§šš¢š§ššš š SMT for both source and S3 sink connectors.
ā
šš©ššš”š š
š„š¢š§š¤ - Demonstrating šš©šš§šš¢š§ššš š integration for both real-time analytics (DataStream API) and data integration (Table API) jobs.
ā
šš©ššš”š šššššš«š - Ingesting streaming data from Flink into a modern lakehouse table.
ā
šš©ššš”š šš©šš«š¤ - Running a batch aggregation job that consumes from the Iceberg table, completing the lineage graph.
This project demonstrates how to build a holistic view of your pipelines, helping answer questions like:
⢠Which applications are consuming this topic?
⢠What's the downstream impact if the topic schema changes?
The whole setup is fully containerized and easy to run.
Want to see it in action? The full source code and a detailed walkthrough are available on GitHub.
ā¢ šššš®š© šš”š ššš¦šØ šš§šÆš¢š«šØš§š¦šš§š:
https://github.com/factorhouse/factorhouse-local
⢠š
šØš« šš”š šš®š„š„ š š®š¢šš šš§š š¬šØš®š«šš ššØšš:
https://github.com/factorhouse/examples/blob/main/projects/data-lineage-labs/lab2_end-to-end.md