Add configurable TARGET_FILE_SIZE for Iceberg tables - #8
Merged
Conversation
sfc-gh-kasher
approved these changes
Sep 9, 2026
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
2 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.
Summary
--target-file-sizeCLI option tosetupcommand, allowing control over theTARGET_FILE_SIZEproperty on Iceberg tables (integer in MB orAUTO, defaultAUTO){{TARGET_FILE_SIZE}}substitutionrunoutput and include it in the results summary JSONTest plan
./iwtpch.sh setup --scale 100 --tables-type iceberg(default AUTO) and verify tables are created successfully./iwtpch.sh setup --scale 100 --tables-type iceberg --target-file-size 16mband verify TARGET_FILE_SIZE is set to 16MB./iwtpch.sh runagainst iceberg tables and confirm file size is printed and included in JSON output--target-file-sizewith invalid input produces a clear error