Skip to content
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

Adding date format to an existing mapping silently fails #3727

Closed
isg8 opened this issue Sep 18, 2013 · 0 comments · Fixed by #3735
Closed

Adding date format to an existing mapping silently fails #3727

isg8 opened this issue Sep 18, 2013 · 0 comments · Fixed by #3735

Comments

@isg8
Copy link

isg8 commented Sep 18, 2013

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.

@ghost ghost assigned spinscale Sep 19, 2013
spinscale added a commit that referenced this issue Nov 19, 2013
In order to be able to add an additional date to a date field mapper,
the merge operation has to support this.

Closes #3727
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants