Update recommendations around working with live data #853
Conversation
This file contains 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
scholtzan
force-pushed
the
update-live-data
branch
from
9d28bb6
to
0a2e550
Compare
scholtzan
force-pushed
the
update-live-data
branch
from
0a2e550
to
41da206
Compare
BenWu
approved these changes
Oct 18, 2024
| - **Recommended Use:** For smaller data volumes and low-complexity queries, or when queries are infrequent. | ||
| - **Pros:** | ||
| - Easy to set up via bigquery-etl | ||
| - **Cons:** |
There was a problem hiding this comment.
Could also list potential duplicate rows as a con like in the scheduled queries section
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.
This updates the docs around working with live date based on the discussion we had in https://docs.google.com/document/d/12uMeJFHak_JpoeI6bKcgV57LrOdHUhNRuG2QwHHfXgM/edit