# Query Conversion from new to old version

**URL:** <https://discuss.elastic.co/t/query-conversion-from-new-to-old-version/159482>\
**Category:** Elasticsearch\
**Created:** [December 5, 2018, 8:16am UTC](https://discuss.elastic.co/t/query-conversion-from-new-to-old-version/159482 "2018-12-05T08:16:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\
**Post date:** [December 5, 2018, 8:16am UTC](https://discuss.elastic.co/t/query-conversion-from-new-to-old-version/159482/1 "2018-12-05T08:16:44Z")

</div>

Hi,

With continuous development on the ES end, we have seen that there are some changes on the ES queries in between different versions. This creates an issue on the application side, requiring some changes in the queries to be made. Is there any mechanism or library through which we can provide compatibility in between some version numbers? I was thinking whether there is a tool which converts the new version query or responses back to older one in order to maintain application compatibility.

Any info in this regard is appreciated.

---

<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:** [January 2, 2019, 8:29am UTC](https://discuss.elastic.co/t/query-conversion-from-new-to-old-version/159482/2 "2019-01-02T08:29:40Z")

</div>

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