Google Symptoms uses metadata to determine how many days of data to fetch #973
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jingjtang
reviewed
Mar 31, 2021
jingjtang
reviewed
Mar 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Instead of pulling a fixed 14 days of data, determine number of days to pull based on metadata
min_lagvalue. Pre-existing functionality (num_export_dayscan be set in params to an integer or to "all") still works.Changelog
min_lagfrom metadata ifnum_export_daysis not set in params.num_export_daysetting from template and Ansible params files.Fixes
Makes GS pipeline more robust to BigQuery outages. Minimize data pulled in anticipation of change to daily updates.