Column Lineage limitations
K processes lineage across numerous sources however there are some scenarios where lineage and the grain of lineage is limited.
This page will cover known limitations and any remediation available or planned.
Issue | Example | Fix | Workaround | |
---|---|---|---|---|
1 | Nested SELECT * from a CTE not supported |
CODE
| Under investigation | Use Bulk Lineage Mapper to map columns between source and target tables. |
2 | SELECT * with Unions not supported |
CODE
| Under investigation | |
3 | Insert into statements currently skipped in processing |
CODE
| Investigation completed. Fix pending. Target release in Q1 25 | |
4 | Copy grants in statements currently causes statement to be skipped in processing |
CODE
| Investigation completed Fix pending Target release in Q1 25 | |
5 | Code that is not currently wrapped in a CREATE statement e.g. DBT code from manifest (represented as a select statement) | Investigation completed Fix pending Target release in Q1 25 |