We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have an existing index with data and mapping with a date field with two existing formats, e.g.:
existing mapping: "tzoffset_timestamp": { "type": "date", "store": true, "format": "EEE MMM dd HH:mm:ss.S Z yyyy||EEE MMM dd HH:mm:ss.SSS Z yyyy", "include_in_all": true }
when executing curl put mapping command with an additional format:
"tzoffset_timestamp": { "type": "date", "store": true, "format": "EEE MMM dd HH:mm:ss.S Z yyyy||EEE MMM dd HH:mm:ss.SSS Z yyyy||yyyy-MM-dd'T'HH:mm:ss.SSSZZ", "include_in_all": true }
succeeds with "ok / acknowledged", yet getting the mapping back provides original two formats.
The text was updated successfully, but these errors were encountered:
513611b
DateFieldMapper.merge() can change date format and include_in_all
6acf519
In order to be able to add an additional date to a date field mapper, the merge operation has to support this. Closes #3727
07d9520
In order to be able to add an additional date to a date field mapper, the merge operation has to support this. Closes elastic#3727
spinscale
Successfully merging a pull request may close this issue.
We have an existing index with data and mapping with a date field with two existing formats, e.g.:
existing mapping:
"tzoffset_timestamp": {
"type": "date",
"store": true,
"format": "EEE MMM dd HH:mm:ss.S Z yyyy||EEE MMM dd HH:mm:ss.SSS Z yyyy",
"include_in_all": true
}
when executing curl put mapping command with an additional format:
succeeds with "ok / acknowledged", yet getting the mapping back provides original two formats.
The text was updated successfully, but these errors were encountered: