Add support for time partitioning and expiry#47
Open
igorwwwwwwwwwwwwwwwwwwww wants to merge 94 commits intocloudflare:masterfrom
Open
Add support for time partitioning and expiry#47igorwwwwwwwwwwwwwwwwwwww wants to merge 94 commits intocloudflare:masterfrom
igorwwwwwwwwwwwwwwwwwwww wants to merge 94 commits intocloudflare:masterfrom
Conversation
…on for WAFRuleIDs (string) and EdgeResponseCompressionRatio (float)
added explicit schema
added logic to read schema from remote JSON file
update schema with additional fields
merge remote-schema
Updated cloud functions storage bucket variable
small typo fix
update README.md
According to [docs](https://cloud.google.com/functions/docs/migrating/nodejs-runtimes) and warning emails > The Node.js 8 runtime will be deprecated on 2020-06-05 At moment I'm connecting our cloudflare to gcp, and decided to set node to 10 can confirm that everything working
upgrade to node 10
add gcp project id module
* Added Spectrum schema and bash $SCHEMA variable. * type fix for Spectrum schema * add $SCHEMA to automatic install * fix README.md * fix capitalization * Update cloudshell.md Co-authored-by: Frank Taylor <7483580+shagamemnon@users.noreply.github.com>
Contributor
|
Hey @igorwwwwwwwwwwwwwwwwwwww thanks for taking a stab at this. In the past, creating ingestion-time partitioning for logs inserted via a load job has been non-trivial. The solution in your PR has not worked in the past (see https://github.com/cloudflare/cloudflare-gcp/blob/add-partition-v2/logpush-to-bigquery/index.js), so we will need a test before a merge can be considered. FWIW: to my knowledge, this can only be accomplished in BigQuery using "partition decorators" which are described here: https://cloud.google.com/bigquery/docs/creating-partitioned-tables#creating_an_ingestion-time_partitioned_table_when_loading_data |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.
The current behaviour is to load everything into a non-partitioned table. That means that queries will scan the entire table every time.
In order to make queries cheaper, we can use time partitioning.
One nice side-effect of this is that we also get the ability to configure expiration.
Note: I could use some help testing out this patch.