Add max_active_partitions support to topic operations #496
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
This PR introduces support for the max_active_partitions parameter in topic control plane operations, providing more precise control over partition auto-merging behavior.
Changes
Added new maxActivePartitions field and corresponding getters/setters in partitioning settings classes
Implemented support for setting and retrieving maxActivePartitions in topic client implementation
Deprecated partitionCountLimit in favor of maxActivePartitions as described in the YDB proto specifications - https://github.com/ydb-platform/ydb/blob/7b288ef1f52ea97c71014dac8ee95bbde82bd6e3/ydb/public/api/protos/ydb_topic.proto#L909