Iceberg: Add support for FILE_SIZE_THRESHOLD to compaction commandFile size threshold #5540
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
difin
force-pushed
the
file_size_threshold
branch
from
eebcfdb to
db5c2ad
Compare
asf-ci-hive
added
tests failed
tests pending
and removed
tests pending
tests failed
labels
difin
force-pushed
the
file_size_threshold
branch
from
db5c2ad to
1af11d1
Compare
asf-ci-hive
added
tests pending
tests unstable
and removed
tests failed
tests pending
labels
difin
force-pushed
the
file_size_threshold
branch
from
1af11d1 to
492883f
Compare
|
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.
What changes were proposed in this pull request?
Add support for FILE_SIZE_THRESHOLD to compaction command and Minor Compaction.
Why are the changes needed?
OPTIMIZE TABLE command syntax includes FILE_SIZE_THRESHOLD and is implemented by other engines (Impala)
Does this PR introduce any user-facing change?
Yes
Is the change a dependency upgrade?
No
How was this patch tested?
New unit tests, integration tests (q-tests)