[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"term-d\u002Fdata-lineage":3,"related-d\u002Fdata-lineage":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fd\u002Fdata-lineage.md","Data Lineage",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"Data lineage is the paper trail that answers where did this number actually come from when a dashboard shows something wrong. It traces a piece of data backward through every transformation, every job, every table it passed through, from the raw source all the way to the chart your boss is currently panicking about.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Data lineage is the tracked history of data as it moves and transforms through a pipeline, recording its origin, the transformations applied, and every downstream table or report it feeds. Lineage tools, like OpenLineage, a dbt project's dependency graph, or a catalog's built-in tracking, make it possible to trace a broken metric back to its root cause and assess the blast radius of a schema change before making it.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Check the lineage graph before you drop that column, three dashboards depend on it.\" \u002F \"We added lineage tracking after a silent upstream change broke half our reports.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"database","Data lineage is the paper trail that answers where did this number actually come from when a dashboard shows something wrong.","intermediate","md","d",{},true,"\u002Fterms\u002Fd\u002Fdata-lineage",[49,50,51,52],"Data Contract","Data Warehouse","Schema Evolution","ETL",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fd\u002Fdata-lineage","YjoRvHs0I5lS2e-pBBczCNbACXfXNJ-1mwqryilFzcc",[60,65,68,71],{"title":49,"path":61,"acronym":6,"category":62,"difficulty":63,"description":64},"\u002Fterms\u002Fd\u002Fdata-contract","architecture","advanced","It's like a pinky promise between two teams, but legally binding (well, technically binding). Team A says 'I promise this data will always have these colum",{"title":50,"path":66,"acronym":6,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fd\u002Fdata-warehouse","A data warehouse is where all your company's data goes to be analyzed.",{"title":52,"path":69,"acronym":6,"category":40,"difficulty":42,"description":70},"\u002Fterms\u002Fe\u002Fetl","ETL stands for Extract, Transform, Load. You extract data from sources, transform it (clean, reshape, calculate), then load it into your warehouse.",{"title":51,"path":72,"acronym":6,"category":40,"difficulty":42,"description":73},"\u002Fterms\u002Fs\u002Fschema-evolution","Your data's shape never actually stays still: new fields show up, old ones get renamed, types change, and yet you've got old data sitting around in the old...",1792528076991]