-
Notifications
You must be signed in to change notification settings - Fork 101
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
[Data Checks Bug]: ETL check checks__fail_firefox_ios_derived__new_profile_activation__v2 failiing to execute due to incorrect check path #4524
Comments
Failed to reproduce this locally. Tried running the following command:
And correctly seeing the following error:
(currently, this is expected as indeed the dataset is missing data for this specific submission_date) This appears to mimic what should be happening in the prod deployment: |
Yielded:
Yielded:
It appears the same command for different submission_dates resulted in different outcomes for the command. For submission dates:
|
It appears the opposite is true for the submission dates when running the When investigating the BQ job id to see further details of the query executed, it appears the query used is completely off from what it is expected to be: This is what the bq console shows as executed SQL:
This is the template we expect to be used: https://github.com/mozilla/bigquery-etl/blob/a30788cdd53d0236dcff139987f2e29db15bde6a/sql/moz-fx-data-shared-prod/firefox_ios_derived/new_profile_activation_v2/checks.sql Which should yield the following query:
|
What is the issue?
What was observed, any logs or relevant links?
ETL task (checks__fail_firefox_ios_derived__new_profile_activation__v2) responsible for validating that the
firefox_ios_derived.new_profile_activation_v2
dataset is correctly being updated currently fails silently with the following error:Example failed run: https://workflow.telemetry.mozilla.org/dags/bqetl_firefox_ios/grid?root=&dag_run_id=scheduled__2023-10-29T04%3A00%3A00%2B00%3A00&tab=logs&task_id=checks__fail_firefox_ios_derived__new_profile_activation__v2
This is unintended behavior, and only got caught by chance when manually attempting to debug an issue with a downstream dataset. This resulted in the task being marked as successful without the dataset checks being executed.
How can we reproduce the bug
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: