Ah, so this is what you mean by idempotent changes - I wanted to prevent
updates when another user had already made a change to that document (to
ensure this change was preserved somehow), but I guess this isn't supported?
Thanks for your help.
On 20 May 2013 12:24, Clinton Gormley clint@traveljury.com wrote:
Chris - you don't need to specify a version. Elasticsearch retrieves the
current document, applies your update and reindexes the document, checking
that the version hasn't been incremented in the meantime. If it has been
incremented, then it retries the process retry_on_conflict times (which
defaults to 0) and either ends up succeeding, or returning a conflict error
to you.You said:
I don't already have the document, but I know what fields I want to
change, and what to change them to - I want to leave all others fields
alone.Right - that's exactly what the update api does.
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/M49krcDGPHc/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.