-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Remove the support for fielddata_fields
#19027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Note that Kibana makes use of fielddata_fields for retrieving the millisecond value of date fields in documents. Is there an alternative for that purpose? |
I guess |
We need to fallback to fielddata for 5.x (at least for old indices), can be removed in 6.0 |
discussed in FixItFriday, the fallback to fielddata for 5.x is only for keyword/text fields. It won't work if the field is numeric since the fielddata for numerics has been removed entirely.
You'll have to ensure that the doc_values are activated on the field otherwise it won't work. This is a side effect of the fielddata removal for numeric fields. Note that this has nothing to do with this issue, this is how the 5.x works and this is not going to change. |
Fielddata for numeric fields were deprecated in 2.0 and removed in 5.0, so doc values would be enabled for any numeric field in an index created in 2.x, unless the user changed the mappings. So we're good to remove fielddata_fields, and kibana will need to change their use of fielddata_fields to |
The parameter fielddata_fields is deprecated and removed in 5.0 elastic/elasticsearch#19027
The parameter fielddata_fields is deprecated and removed in 5.0 elastic/elasticsearch#19027
|
Closed by #25537 |
The parameter
fielddata_fields
is deprecated (#18943) but we continue to fallback to the fielddata cache when the docvalues are not enabled on the field.We should remove the ability to retrieve the fields through the fielddata cache because the output is not equivalent to the docvalue and may greatly differ from the stored field.
The text was updated successfully, but these errors were encountered: