# What is compatible version to upgrade from 1.3.4 without any existing api changes

**URL:** <https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478>\
**Category:** Elasticsearch\
**Created:** [March 25, 2016, 9:09pm UTC](https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478 "2016-03-25T21:09:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dany](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dany/32/8131_2.png) [@dany](https://discuss.elastic.co/u/dany)\
**Post date:** [March 25, 2016, 9:09pm UTC](https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478/1 "2016-03-25T21:09:17Z")

</div>

I understand there might not be a direct answer for this. Some suggestion would be very helpful.

I would like to upgrade from my current elasticsearch version 1.3.4 to some version above 1.7 or 1.7 itself. I would like to use the features like delayed timeout and synced flush.

But I am not sure which is the comaptible version [with minimal changes]. Could someone help me with this?

---

<div class="post-metadata">

**Author:** ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)\
**Post date:** [March 25, 2016, 9:43pm UTC](https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478/2 "2016-03-25T21:43:38Z")

</div>

Hi, dany,

I would recommend two things:

1. review breaking changes for each version: [https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes.html)
2. create a test environment and try to emulate your production environment, including deployment, configuration, data load, and all client interaction, to see if you get broken or unexpected behavior

Glen

---

<div class="post-metadata">

**Author:** ![dany](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dany/32/8131_2.png) [@dany](https://discuss.elastic.co/u/dany)\
**Post date:** [March 29, 2016, 7:34pm UTC](https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478/3 "2016-03-29T19:34:50Z")

</div>

Thanks for the suggestion Glen. I went through the breaking changes and and decided to upgrade to 1.7. Because 2.0 doesn't have facets which we use mainly in our app.

---

<div class="post-metadata">

**Author:** ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)\
**Post date:** [March 30, 2016, 2:58pm UTC](https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478/4 "2016-03-30T14:58:21Z")

</div>

You should migrate your facets to aggregations whenever you have the time.

---

<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 5, 2017, 11:04pm UTC](https://discuss.elastic.co/t/what-is-compatible-version-to-upgrade-from-1-3-4-without-any-existing-api-changes/45478/5 "2017-07-05T23:04:01Z")

</div>