<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Lineage on Pi Stack</title><link>https://www.pistack.xyz/tags/data-lineage/</link><description>Recent content in Data-Lineage on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/data-lineage/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenLineage vs DataHub vs Apache Atlas: Self-Hosted Data Lineage Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-20-openlineage-vs-datahub-vs-apache-atlas-self-hosted-data-lineage-guide-2026/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-20-openlineage-vs-datahub-vs-apache-atlas-self-hosted-data-lineage-guide-2026/</guid><description>&lt;p>Data lineage — the ability to track where data comes from, how it transforms, and where it ends up — has become essential for any organization running non-trivial data pipelines. When a dashboard shows a wrong number, lineage tells you exactly which upstream table, job, or transformation introduced the error. When regulators ask where personal data flows, lineage provides the audit trail.&lt;/p></description></item></channel></rss>