We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://cloud.google.com/bigquery/docs/clustered-tables. It can make some queries cheaper and faster.
The text was updated successfully, but these errors were encountered:
I was thinking of this when reading @askeluv 's blog post: https://towardsdatascience.com/how-to-get-any-ethereum-smart-contract-into-bigquery-in-8-mins-bab5db1fdeee If we implement clustering/partitioning, it should be possible to reduce the query cost of using the logs table directly, i.e. no need to create contract-specific tables.
logs
However, there is some active work being done for streaming into partitions, see: https://issuetracker.google.com/issues/35905817#comment89
Sorry, something went wrong.
That's a good idea.
No branches or pull requests
https://cloud.google.com/bigquery/docs/clustered-tables. It can make some queries cheaper and faster.
The text was updated successfully, but these errors were encountered: