Versioning: Check for conflicts when updating specific fields only

Hi,

in Elasticsearch Platform — Find real-time answers at scale | Elastic it
says:

Note that the versioning check is completely optional. You can choose to
enforce it while updating certain fields (like votes) and ignore it when
you update others (typically text fields, like name). It all depends on the
requirements of your application and your tradeoffs.

How can I define which fields to ignore / to be affected by versioning in
my mapping?
Thanks, Joa

--
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.

You can't do it server side, your client code has to decide whether to
opt-in to versioning check or not

On Sun, Nov 3, 2013 at 12:55 AM, joa joafeldmann@gmail.com wrote:

Hi,

in Elasticsearch Platform — Find real-time answers at scale | Elastic it
says:

Note that the versioning check is completely optional. You can choose to
enforce it while updating certain fields (like votes) and ignore it when
you update others (typically text fields, like name). It all depends on the
requirements of your application and your tradeoffs.

How can I define which fields to ignore / to be affected by versioning in
my mapping?
Thanks, Joa

--
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.

--
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.