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
Unable to configure eager fielddata loading for _timestamp field via PUT mapping API for type with existing mapping #6958
Comments
Hi @shikhar What version are you using? Also, could you provide a small curl recreation of the problem? thanks |
acknowledged: true but:
|
forgot to mention, this is on ES 1.3.0 |
The fielddata settings are not merged when the mapping is updated (https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/index/mapper/internal/TimestampFieldMapper.java#L280). This is similar to issue #777 and #5772. I will go through all the different root mappers and fix one by one, just have not gotten further than |
Updates on the _timestamp field were silently ignored. Now _timestamp undergoes the same merge as regular fields. This includes exceptions if a prroperty cannot be changed. "path" and "default" cannot be changed. closes elastic#5772 closes elastic#6958 partially fixes elastic#777
When creating a new index, if I have eager fielddata loading configured for the
_timestamp
field, that sticks.However when updating this setting via the PUT mapping API, although the request is acknowledged when I check the mapping via GET, fielddata configuration for that field is blank.
I have been able to successfully configure it for other fields via the PUT mapping API, though. Seems like this problem may be specific to the special underscore-prefixed fields, though I've only really tried
_timestamp
.The text was updated successfully, but these errors were encountered: