Skip to content

Two empty mappings now are created equally#107936

Merged
piergm merged 15 commits intoelastic:mainfrom
piergm:Two-empty-mappings-reported-differently-in-field_caps
Sep 12, 2024
Merged

Two empty mappings now are created equally#107936
piergm merged 15 commits intoelastic:mainfrom
piergm:Two-empty-mappings-reported-differently-in-field_caps

Conversation

@piergm
Copy link
Copy Markdown
Member

@piergm piergm commented Apr 26, 2024

Mapping defaults to {} aka EMPTY_MAPPING, even if mappings: {} is passed in the request body to match the behaviour when passing empty mapping on index create.
Prior to this change mappings: {} was instead wrapped with with _doc
fixes #107031

@piergm piergm added >bug :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Meta label for search team v8.15.0 labels Apr 26, 2024
@piergm piergm self-assigned this Apr 26, 2024
@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-search (Team:Search)

@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

Hi @piergm, I've created a changelog YAML for you.

@elasticsearchmachine elasticsearchmachine added v8.16.0 Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch and removed v8.15.0 labels Jul 4, 2024
@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-search-foundations (Team:Search Foundations)

@elasticsearchmachine elasticsearchmachine removed the Team:Search Meta label for search team label Jul 4, 2024
@javanna
Copy link
Copy Markdown
Contributor

javanna commented Jul 30, 2024

@piergm does this need review?

@piergm piergm requested a review from a team as a code owner September 4, 2024 09:50
@costin
Copy link
Copy Markdown
Member

costin commented Sep 12, 2024

Is it possible to get this bug fixed and backported to 8.x in the near future ? The fix looks contained and the bug keeps occurring every now and then. Thanks!

@piergm piergm added the auto-backport Automatically create backport pull requests when merged label Sep 12, 2024
@piergm piergm merged commit cd8d37b into elastic:main Sep 12, 2024
@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

An unhandled error occurred. Please consult the logs

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 107936

piergm added a commit to piergm/elasticsearch that referenced this pull request Sep 12, 2024
* Two empty mappings reported equally in field_caps

* empty mapping now is {}

* iter

(cherry picked from commit cd8d37b)
@piergm
Copy link
Copy Markdown
Member Author

piergm commented Sep 12, 2024

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

davidkyle pushed a commit that referenced this pull request Sep 12, 2024
* Two empty mappings reported equally in field_caps

* empty mapping now is {}

* iter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >bug :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch v8.16.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Two "empty" mappings reported differently in field_caps

6 participants