Skip to content

Clarify dynamic mapping behavior in Elasticsearch quick start - #8187

Draft
georgewallace with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-quick-starts-documentation
Draft

Clarify dynamic mapping behavior in Elasticsearch quick start#8187
georgewallace with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-quick-starts-documentation

Conversation

Copilot AI commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

The Elasticsearch quick start page describes dynamic: true in a way that can be read as if mappings do not change when new fields are indexed. This update makes the behavior explicit: new fields cause the mapping to update dynamically.

  • Problem

    • The Combine dynamic and explicit mappings section used wording that blurred the distinction between manually updating a mapping and Elasticsearch dynamically adding fields to it.
  • Change

    • Reworded the affected sentence in solutions/search/get-started/index-basics.md to state that, when dynamic is true, the mapping updates dynamically as new fields are added to documents.
    • Kept the surrounding explanation and page structure unchanged.
  • Updated wording

    When an index has the `dynamic` flag set to `true`, the mapping updates dynamically when you add new fields to documents, which allows you to combine explicit and dynamic mappings.

Co-authored-by: georgewallace <6796566+georgewallace@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix misleading explanation in Quick starts documentation Clarify dynamic mapping behavior in Elasticsearch quick start Sep 3, 2026
Copilot AI requested a review from georgewallace September 3, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Website]: 关于官方文档中Quick starts中Combine dynamic and explicit mappings存在误导性说明的问题

2 participants