Column Description Propagation ✨
How Catalog leverages Column Lineage to increase documentation coverage
It is frequent for a column to be reused "as is" by downstream tables. In that case, the column will be called in the "Select" SQL clause, without any modification.
In that case, why should you document the downstream columns? You're right, you should not have to! And Catalog solves that for you this way:
In the picture below, user.account_id
inherits its description from its parent column in the opportunity
table

Last updated
Was this helpful?