You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you create an index, put a doc into it, and then try to update the mapping to enable _timestamp and set store:true, you will notice that the response comes back as acknowledged:true with no error messages. But if you get the _mapping back, you will notice that store:true is not set (by design because we do not allow changing the store parameter post indexing).
For regular properties, if you attempt to update its store parameter post indexing, it will actually throw a 400 error indicating a MergeMappingException because of differences in store values.
It will be nice to add the same validation and throw a similar error when users attempt to update the store value of _timestamp post-indexing.
The text was updated successfully, but these errors were encountered:
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.
closeselastic#5772closeselastic#6958
partially fixeselastic#777
Updates on the _timestamp field were silently ignored.
Now _timestamp undergoes the same merge as regular
fields. This includes exceptions if a property cannot
be changed.
"path" and "default" cannot be changed.
closes#5772closes#6958closes#7614
partially fixes#777
If you create an index, put a doc into it, and then try to update the mapping to enable _timestamp and set store:true, you will notice that the response comes back as acknowledged:true with no error messages. But if you get the _mapping back, you will notice that store:true is not set (by design because we do not allow changing the store parameter post indexing).
For regular properties, if you attempt to update its store parameter post indexing, it will actually throw a 400 error indicating a MergeMappingException because of differences in store values.
It will be nice to add the same validation and throw a similar error when users attempt to update the store value of _timestamp post-indexing.
The text was updated successfully, but these errors were encountered: