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(glam) add fully qualified table names in legacy telemetry queries #5559
Conversation
telemetry_derived.clients_histogram_aggregates_v2 | ||
`moz-fx-data-shared-prod.telemetry_derived.clients_histogram_aggregates_v2` | ||
WHERE | ||
submission_date = DATE_SUB(DATE(@submission_date), INTERVAL 1 DAY) |
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 added this parameter to be extra safe. The table is overwritten at every execution so there should only be one submission date, but just in case there are more...
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.
Only formatting in this file
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
dc2824d
to
1a35b29
Compare
This comment has been minimized.
This comment has been minimized.
1a35b29
to
77b33d1
Compare
This comment has been minimized.
This comment has been minimized.
Integration report for "Merge branch 'main' into glam-fully-qual-tbls"
|
Most of the changes are formatting.
This PR adds fully qualified table names to GLAM ETL Legacy queries.
... and there's one
@submission_date
parameter I smuggled, to be extra safe.Checklist for reviewer:
<username>:<branch>
of the fork as parameter. The parameter will also show upin the logs of the
manual-trigger-required-for-fork
CI task together with more detailed instructions.For modifications to schemas in restricted namespaces (see
CODEOWNERS
):┆Issue is synchronized with this Jira Task