# Stability of Update By Query **URL:** \ **Category:** Elasticsearch\ **Created:** [September 20, 2016, 1:48pm UTC](https://discuss.elastic.co/t/stability-of-update-by-query/61018 "2016-09-20T13:48:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Zaid\_Amir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zaid_amir/32/54679_2.png) [@Zaid\_Amir](https://discuss.elastic.co/u/Zaid_Amir)\ **Post date:** [September 20, 2016, 1:48pm UTC](https://discuss.elastic.co/t/stability-of-update-by-query/61018/1 "2016-09-20T13:48:02Z")
Hi, I am currently running a production cluster with ES 1.7 installed. currently I rely on the [UpdateByQuery plugin](https://github.com/yakaz/elasticsearch-action-updatebyquery) and since the release of ES 2.0 there has not been an update to that plugin to support ES 2.X. I noticed a while back that the functionality is now baked in ES with the new [Update By Query API](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-update-by-query.html) The only problem that is preventing me from upgrading to the latest ES version is the warning displayed at the top of the API's documentation stating that this API should be considered experimental. I know that changes can be made to the API in future versions and that is fine by me but I was wondering how stable the API currently is for a production cluster. I have done some small tests with the API and it all seems to be working fine but I was wondering if there are any known issues, limitations or bugs with the current version. Best regards ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [September 20, 2016, 2:06pm UTC](https://discuss.elastic.co/t/stability-of-update-by-query/61018/2 "2016-09-20T14:06:53Z")
> [@Zaid\_Amir](#): > > considered experimental This is our little out for semver - we're not yet confident enough in the API to guarantee that we won't make breaking changes to it in a minor release. We think we might find things that are super important that we'll _have_ to add or remove. We aren't going to do anything like that in a patch release though. And we're not going to make backwards incompatible changes lightly either. So you should be quite safe using so long as you test your application before upgrading Elasticsearch which you should do anyway. Maybe just be extra careful. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [September 20, 2016, 2:25pm UTC](https://discuss.elastic.co/t/stability-of-update-by-query/61018/3 "2016-09-20T14:25:13Z")
Also if you read the very first lines of the plugin you were using: > The update by query API allows all documents that with the query to be updated with a script. **This is experimental.** 🙂 ---
**Author:** ![Zaid\_Amir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zaid_amir/32/54679_2.png) [@Zaid\_Amir](https://discuss.elastic.co/u/Zaid_Amir)\ **Post date:** [September 20, 2016, 2:26pm UTC](https://discuss.elastic.co/t/stability-of-update-by-query/61018/4 "2016-09-20T14:26:51Z")
Yes I know that and I had the same discussion before with the authors about that particular thing. I always panic when I hear the word 'experimental;' 😉 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:18pm UTC](https://discuss.elastic.co/t/stability-of-update-by-query/61018/5 "2017-07-05T22:18:45Z")