Skip to content

[9.1] @kbn/storage-adapter: do not update settings when updating mappings (#232840)#240194

Merged
jloleysens merged 1 commit into
elastic:9.1from
jloleysens:backport/9.1/pr-232840
Oct 24, 2025
Merged

[9.1] @kbn/storage-adapter: do not update settings when updating mappings (#232840)#240194
jloleysens merged 1 commit into
elastic:9.1from
jloleysens:backport/9.1/pr-232840

Conversation

@jloleysens
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…elastic#232840)

## Summary

Fix a bug causing a mapping update of a `index-storage` to cause an
error during `updateMappingsOfExistingIndex`.

During that phase, we were trying to update the index's settings in
addition to its mappings. However, the `simulateIndexTemplate` API
returns the full set of settings, and not only the ones which can be
updated, so the following `putSettings` call was failing with errors
such as:

```
 Root causes:
                illegal_argument_exception: can not update private setting [index.allocation.existing_shards_allocator]; this setting is managed by Elasticsearch
```

Given there is apparently no proper way to identify which setting(s) are
private vs which ones can be updated, this PR simply fully disables the
setting update part, as discussed with @elastic/kibana-core.

(cherry picked from commit 55c1587)
@jloleysens jloleysens added the backport This PR is a backport of another PR label Oct 23, 2025
@jloleysens jloleysens enabled auto-merge (squash) October 23, 2025 07:24
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

@jloleysens jloleysens merged commit 0964937 into elastic:9.1 Oct 24, 2025
16 checks passed
@jloleysens jloleysens deleted the backport/9.1/pr-232840 branch October 24, 2025 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants