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
Mapping: Fix possibility of losing meta configuration on field mapping update #5053
Comments
version 0.90.3 |
Hey I cannot reproduce this with any of the 0.90 release (tried .0, .3 and .11). The URLs you provided are not valid (must be Thanks! |
Sorry, formatting fail :). Have updated the CURLs. Thanks. |
any update? I'll fix this if not |
Whoah, I just ran into this today. Heres my test case: I´m running version 1.1.2 Is that expected behaviour or a bug? |
hey there, this looks like a bug indeed from a birds eye view, I will take a look as soon as I can! |
…g update The TTL, size, timestamp and index meta properties could be lost on an update of a single field mapping due to a wrong comparison in the merge method (which was caused by a wrong initialization, which marked an update as explicitely disabled instead of unset. Closes elastic#5053
…g update The TTL, size, timestamp and index meta properties could be lost on an update of a single field mapping due to a wrong comparison in the merge method (which was caused by a wrong initialization, which marked an update as explicitely disabled instead of unset. Closes #5053
…g update The TTL, size, timestamp and index meta properties could be lost on an update of a single field mapping due to a wrong comparison in the merge method (which was caused by a wrong initialization, which marked an update as explicitely disabled instead of unset. Closes #5053
…g update The TTL, size, timestamp and index meta properties could be lost on an update of a single field mapping due to a wrong comparison in the merge method (which was caused by a wrong initialization, which marked an update as explicitely disabled instead of unset. Closes elastic#5053
Create a new schema with a field and the _timestamp field enabled:
curl -XPOST http://localhost:9200/foo -d '
{
"mappings": {
"product": {
"_timestamp" : { "enabled" : true },
"properties": {
"field1": { "type": "integer" }
}
}
}
}'
Retrieve the mapping, all looks good:
curl http://localhost:9200/foo/_mapping
{"foo":{"product":{"_timestamp":{"enabled":true},"properties":{"field1":{"type":"integer"}}}}}
Now add another field:
curl -XPUT http://localhost:9200/foo/product/_mapping -d '
{
"product" : {
"properties": {
"field2" : {"type" : "integer" }
}
}
}
'
Get the mapping again:
curl http://localhost:9200/foo/_mapping
{"foo":{"product":{"properties":{"field1":{"type":"integer"},"field2":{"type":"integer"}}}}}
The _timestamp field is gone!
The text was updated successfully, but these errors were encountered: