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
Currently, the LinkedMapWritable that comes into the mapper is purely the _source field from the response. It would be great if this data structure could also contain the _version.
In a write back scenario, with optimistic locking, I need to hit the GET API for each map input in order to get the _version field before I do a write back to ES. This of course adds O(n) operation for a data point that could come along with the initial stream.
Does this seem like a reasonable thing to add?
The text was updated successfully, but these errors were encountered:
mgreene
changed the title
Allow LinkedMapWritable to include document meta fields like version
Allow LinkedMapWritable to include document meta fields like _version
Sep 5, 2014
This is now supported in master through es.read.metadata field - setting it to true will add the metadata under _metadata field (customizable) into the LinkedHashMap. Supported across integrations
Currently, the
LinkedMapWritable
that comes into the mapper is purely the_source
field from the response. It would be great if this data structure could also contain the_version
.In a write back scenario, with optimistic locking, I need to hit the GET API for each map input in order to get the
_version
field before I do a write back to ES. This of course adds O(n) operation for a data point that could come along with the initial stream.Does this seem like a reasonable thing to add?
The text was updated successfully, but these errors were encountered: