# Versioning: Check for conflicts when updating specific fields only **URL:** \ **Category:** Elasticsearch\ **Created:** [November 2, 2013, 10:55pm UTC](https://discuss.elastic.co/t/versioning-check-for-conflicts-when-updating-specific-fields-only/14230 "2013-11-02T22:55:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![joa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joa/32/1807_2.png) [@joa](https://discuss.elastic.co/u/joa)\ **Post date:** [November 2, 2013, 10:55pm UTC](https://discuss.elastic.co/t/versioning-check-for-conflicts-when-updating-specific-fields-only/14230/1 "2013-11-02T22:55:31Z")
Hi, in [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/elasticsearch-versioning-support/) 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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [November 2, 2013, 11:00pm UTC](https://discuss.elastic.co/t/versioning-check-for-conflicts-when-updating-specific-fields-only/14230/2 "2013-11-02T23:00:07Z")
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](mailto:joafeldmann@gmail.com) wrote: > Hi, > > in [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/elasticsearch-versioning-support/) 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:09am UTC](https://discuss.elastic.co/t/versioning-check-for-conflicts-when-updating-specific-fields-only/14230/3 "2017-07-06T02:09:11Z")
Closed on July 6, 2017, 2:09am UTC