docs: mark data.autocomplete.* settings as deprecated since 8.3.0#269868
Merged
florent-leborgne merged 10 commits intoMay 21, 2026
Conversation
Contributor
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
Co-authored-by: Cursor <cursoragent@cursor.com>
…plete.* settings Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- data.autocomplete.* settings: ech: ga (all three generations are explicitly allowlisted in ECH, not unavailable) - unifiedSearch.autocomplete.* settings: stack: ga 8.3 to reflect when these became the canonical replacement settings Co-authored-by: Cursor <cursoragent@cursor.com>
florent-leborgne
added
Team:Docs
release_note:skip
|
Pinging @elastic/experience-docs (Team:Docs) |
Contributor
💚 Build Succeeded
|
mmahacek
approved these changes
May 19, 2026
natasha-moore-elastic
approved these changes
May 21, 2026
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
May 22, 2026
…lastic#269868) ## Summary This PR addresses elastic/docs-content#6511. The page [General settings in Kibana](https://www.elastic.co/docs/reference/kibana/configuration-reference/general-settings) lists \`data.autocomplete.valueSuggestions.terminateAfter\` and \`data.autocomplete.valueSuggestions.timeout\` without any deprecation indicator, making them appear as valid current settings. These settings were deprecated in Kibana 8.3.0 when the autocomplete logic was moved from the \`data\` plugin to the \`unified_search\` plugin (now \`kql\`) via [elastic#129977](elastic#129977). The canonical settings since 8.3.0 are \`unifiedSearch.autocomplete.valueSuggestions.terminateAfter\` and \`unifiedSearch.autocomplete.valueSuggestions.timeout\`. The backward-compatible deprecation handler (which remaps the old keys to the new ones with a warning) was accidentally removed in [elastic#246674](elastic#246674) and restored in [elastic#268872](elastic#268872) (backported to v9.4.2 and v9.5.0). During the window between 9.4.0 and 9.4.1, customers using \`data.autocomplete.*\` in \`kibana.yml\` experienced startup failures. All three generations of the settings (\`kibana.*\`, \`data.*\`, \`unifiedSearch.*\`) are explicitly allowlisted in ECH and work for users on ECH deployments. ## Changes - **\`docs/reference/configuration-reference/general-settings.yml\`**: - Marks \`data.autocomplete.valueSuggestions.terminateAfter\` and \`data.autocomplete.valueSuggestions.timeout\` as \`deprecated 8.3\` on stack, with \`deprecation_details\` pointing to the \`unifiedSearch.*\` replacements. - Adds an inline note on both deprecated settings warning that using them in Kibana 9.4.0–9.4.1 causes a startup failure, and advising users to migrate or upgrade. - Adds \`unifiedSearch.autocomplete.valueSuggestions.timeout\` and \`unifiedSearch.autocomplete.valueSuggestions.terminateAfter\` as \`stack: ga 8.3\` entries so the canonical settings are properly documented. ## Resolves Closes elastic/docs-content#6511 --- > **AI-assisted draft** — created with Claude Sonnet 4.6 in Cursor. > Review all generated content for factual accuracy before merging. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
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
4 participants
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 addresses elastic/docs-content#6511.
The page General settings in Kibana lists `data.autocomplete.valueSuggestions.terminateAfter` and `data.autocomplete.valueSuggestions.timeout` without any deprecation indicator, making them appear as valid current settings.
These settings were deprecated in Kibana 8.3.0 when the autocomplete logic was moved from the `data` plugin to the `unified_search` plugin (now `kql`) via #129977. The canonical settings since 8.3.0 are `unifiedSearch.autocomplete.valueSuggestions.terminateAfter` and `unifiedSearch.autocomplete.valueSuggestions.timeout`.
The backward-compatible deprecation handler (which remaps the old keys to the new ones with a warning) was accidentally removed in #246674 and restored in #268872 (backported to v9.4.2 and v9.5.0). During the window between 9.4.0 and 9.4.1, customers using `data.autocomplete.*` in `kibana.yml` experienced startup failures.
All three generations of the settings (`kibana.`, `data.`, `unifiedSearch.*`) are explicitly allowlisted in ECH and work for users on ECH deployments.
Changes
Resolves
Closes elastic/docs-content#6511