This repository was archived by the owner on Jan 27, 2020. It is now read-only.
Splitting Schedoscope views service call with Option all#200
Open
utzwestermann wants to merge 2 commits into
Open
Splitting Schedoscope views service call with Option all#200utzwestermann wants to merge 2 commits into
utzwestermann wants to merge 2 commits into
Conversation
added 2 commits
May 9, 2018 12:08
called with all option. Added UUID path prefix to BigQuery export bucket path to avoid potential data duplication by stale export files in bucket in case of terminated jobs
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
When views operation is called in SchedoscopeServiceImpl with option all set, only aggregate table data is returned and not view data. To obtain view data, issue a second call without the all option.
Also, when exporting to BigQuery, a UUID path prefix is used for storing exported data in Cloud Storage. This avoids clashes with remnants of terminated previous job runs, which in turn may result in data duplication.