-
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
feat(ingest): add escape hatch methods to SqlParsingAggregator #9860
Conversation
query_fingerprint = get_query_fingerprint( | ||
known_query_lineage.query_text, self.platform.platform_name | ||
) | ||
# TODO format the query text? |
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 formatting the query might be useful if we don't do it on the frontend side when we are showing the queries, but it should be optional.
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.
yeah I will do it in a future PR
QueryMetadata( | ||
query_id=query_fingerprint, | ||
formatted_query_string=known_query_lineage.query_text, | ||
session_id=_MISSING_SESSION_ID, |
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.
Is there a value if we can pass in session id to the know lineage as well?
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.
In some case I think we should be able to capture
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.
yup I'll add that in the next PR
Checklist