Fix bugs with index.number_of_routing_shards
setting. (#109656)
#109658
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
This PR addresses the issues outlined in issue #109656 regarding the
index.number_of_routing_shards
setting. The key fixes include:index.number_of_routing_shards
matches the computed value ofrouting_num_shards
.index.number_of_routing_shards
after index creation._settings
API correctly returns the value ofindex.number_of_routing_shards
.Self-Tests After Fix
Test 1: Default Value Alignment
Test 2: Immutability Enforcement
Test 3: Explicit Setting Retrieval
Summary
This fix ensures that the
index.number_of_routing_shards
setting is correctly set and retrieved, and enforces its immutability post-creation. Therouting_num_shards
remains an internal setting, as originally designed, and does not require modification.