-
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(ingestion/bigquery): Use sqlglot_lineage for usage and add more perf timers #9247
feat(ingestion/bigquery): Use sqlglot_lineage for usage and add more perf timers #9247
Conversation
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.
Can you break this down by both? i.e. one timer for sql parsing, another for store_usage_event?
@@ -395,7 +398,10 @@ def resolve_table(self, table: _TableName) -> Tuple[str, Optional[SchemaInfo]]: | |||
if schema_info: | |||
return urn_lower, schema_info | |||
|
|||
return urn_lower, None | |||
if self.platform in CASE_SENSITIVE_PLATFORMS: |
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.
rename to TABLE_CASE_SENSITIVE_PLATFORMS
sql_query, | ||
flags=re.IGNORECASE, | ||
) | ||
class BigQuerySQLParser: |
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.
add a comment that this is unused and purely for tests for now
maybe move to the tests/ directory?
@asikowitz would love to get this merged since the changes are good and I don't want them to get stale |
Thanks for the reminder |
Checklist