# Resolving version conflicts for UpdateByQuery in Elasticsearch

**URL:** <https://discuss.elastic.co/t/resolving-version-conflicts-for-updatebyquery-in-elasticsearch/138180>\
**Category:** Elasticsearch\
**Created:** [July 2, 2018, 10:51am UTC](https://discuss.elastic.co/t/resolving-version-conflicts-for-updatebyquery-in-elasticsearch/138180 "2018-07-02T10:51:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![manubhogal19](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@manubhogal19](https://discuss.elastic.co/u/manubhogal19)\
**Post date:** [July 2, 2018, 10:51am UTC](https://discuss.elastic.co/t/resolving-version-conflicts-for-updatebyquery-in-elasticsearch/138180/1 "2018-07-02T10:51:03Z")

</div>

I need to implement UpdateByQuery on large dataset, on a server which is updated by various nodes very frequently. This results in version control issues for a lot of documents. Also, retry\_on\_conflict is not the solution I am looking for, as I have already implemented it,and still I lose some documents.

Is there a way,using scripts or otherwise,that allows me to update documents even if specified version is less than current version ?  
Any help is much appreciated.  
Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 30, 2018, 10:51am UTC](https://discuss.elastic.co/t/resolving-version-conflicts-for-updatebyquery-in-elasticsearch/138180/2 "2018-07-30T10:51:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.