-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Deprecate fielddata on _id/_uid #25240
Copy link
Copy link
Closed
Labels
:Search/SearchSearch-related issues that do not fall into other categoriesSearch-related issues that do not fall into other categoriesblockerdiscussv6.0.0-beta1
Description
Some features like random_score use fielddata on _id and our documentation sometimes recommends to sort on _id in order to have a stable sort across pages (eg. https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-search-after.html). However fielddata on such unique fields has a huge cost if you have significant amounts of data, we should move away from it.
We probably have two options here, which are to either add doc values to _id (#11887) but this proved controversial due to the overhead it adds to the index, or switch to _doc but this has the drawback of not being comparable across shards or after merges.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Search/SearchSearch-related issues that do not fall into other categoriesSearch-related issues that do not fall into other categoriesblockerdiscussv6.0.0-beta1
Type
Fields
Give feedbackNo fields configured for issues without a type.