fix(ingest/powerbi): strip Athena catalog prefix from ODBC column lineage URNs #15746
+249
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
awsdatacatalog.catalog prefix from column lineage URNs to match existing entitiesProblem
When PowerBI connects to Athena via ODBC, SQL queries reference tables as
awsdatacatalog.database.table. The previous fix (#15728) only stripped this prefix from table-level lineage URNs, but column-level lineage URNs still contained the prefix, causing lineage to not connect to existing Athena/Glue entities.Solution
Updated
_strip_athena_catalog_from_lineage()inOdbcLineageto strip catalog prefix from both:lineage.upstreams[*].urn(table-level)lineage.column_lineage[*].upstreams[*].table(column-level)Scope