Remove max rows per segment from compaction dialog#10404
Closed
ccaominh wants to merge 2 commits intoapache:masterfrom
Closed
Remove max rows per segment from compaction dialog#10404ccaominh wants to merge 2 commits intoapache:masterfrom
ccaominh wants to merge 2 commits intoapache:masterfrom
Conversation
Configuring autocompaction with single_dim partitioning in the web console, requires specifying maxRowsPerSegment in the "Tuning config" field, rather than the "Max rows per segment" field. Specifying maxRowsPerSegment in the "Tuning config" also works for dynamic and hash partitions. To make the workflow consistent for all partitioning schemes, remove the "Max rows per segment" field so that the value is always specified in the "Tuning config" field.
Contributor
Author
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
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.
Description
Configuring auto compaction with single_dim partitioning in the web console, requires specifying
maxRowsPerSegmentin the "Tuning config" field, rather than the "Max rows per segment" field. SpecifyingmaxRowsPerSegmentin the "Tuning config" also works for dynamic and hash partitions. To make the workflow consistent for all partitioning schemes, remove the "Max rows per segment" field so that the value is always specified in the "Tuning config" field.Before
After
This PR has: