Feature: configurable BigQuery offline store export parquet file size #12
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
vstrimaitis
reviewed
Nov 7, 2023
Co-authored-by: Daniel Salvador <[email protected]>
vstrimaitis
approved these changes
Nov 7, 2023
GytisBraz
approved these changes
Nov 7, 2023
danielsalvador
approved these changes
Nov 7, 2023
KarolisKont
deleted the
feature/bq_config_size_remote_export_parquet_file
branch
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.
It's a hackish solution, but it operates as follows: you specify your expected export Parquet file size in Megabytes through the
BQ_EXPORT_PARQUET_FILE_SIZE_MBenvironment variable, the value must not exceed 1000 and should be numeric digit. If you do not set this environment variable, it will default to the previous behavior, allowing the BigQuery exporter function to determine the export file size.