-
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/bigquery): fix lineage if multiple sql expression passed in and destination table set #10212
fix(ingest/bigquery): fix lineage if multiple sql expression passed in and destination table set #10212
Conversation
…table set explicitly on the query UI
)""" | ||
else: | ||
query = e.query | ||
except Exception: |
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.
now that we have the other PR merged, we should be able to revert this?
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.
This part is not full because we still need to wrap it into a create statement and get the last statement from the query.
The sanitized table name can be reverted but do you think it can cause any harm if we do here as well?
…n and destination table set (datahub-project#10212) Co-authored-by: Harshal Sheth <hsheth2@gmail.com>
fix lineage if multiple sql expression passed in and destination table set on the query UI
Checklist