-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ingest/snowflake): missing view downstream cll if platform instance is set #8966
fix(ingest/snowflake): missing view downstream cll if platform instance is set #8966
Conversation
upstream_column_info.table | ||
).get_dataset_name() | ||
if self.config.platform_instance and upstream_table_id.startswith( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this happen? Perhaps we should separate platform instance out in the sql parser instead? cc @hsheth2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imo the ideal outcome would be for the sql parser to respect platform_instance
if one is passed in to the schema resolver
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought it already does that, but might be wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the sql lineage returned has
- dataset urn - with platform_instance
- column to column lineage where each column is represented by (dataset urn, column_name)
What's missing here is that - we don't have raw dataset name (or fully qualified name) without platform instance in the upstream result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hsheth2 @asikowitz any thoughts on how to proceed here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, this bug in snowflake view lineage can also be solved by converting sql parsing result to fine grained lineage directly instead of raw snowflake data models again. Let me attempt that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. @hsheth2 please check now.
9dcd287
to
dab2eed
Compare
@mayurinehate looks like there's a conflict on this PR |
Resolved. |
Checklist