# Notice - Gateway changes in next version

**URL:** <https://discuss.elastic.co/t/notice-gateway-changes-in-next-version/2968>\
**Category:** Elasticsearch\
**Created:** [May 24, 2010, 7:36pm UTC](https://discuss.elastic.co/t/notice-gateway-changes-in-next-version/2968 "2010-05-24T19:36:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 24, 2010, 7:36pm UTC](https://discuss.elastic.co/t/notice-gateway-changes-in-next-version/2968/1 "2010-05-24T19:36:58Z")

</div>

Hi,

I thought long and hard about this one, and decided to do it in order to  
better support future elasticsearch version. I have changed the format of  
the gateway storage to allow to support for easily changing it without  
breaking backward compatibility. I consider gateway changes as something  
that needs to be frowned upon, and I apologize in advance for this change.  
This means that upgrading to the next version will require a reindexing of  
the data, booting from a clean gateway storage.

For this reason, the next version will be 0.8 (which includes several  
improvements, the most important one is a workaround for a Lucene bug in  
memory management). I am trying to see if I can beef it up a bit more with  
features, so it will deserve the 0.8 release (aside from the HDFS gateway),  
but it won't linger for long (hopefully, at max, a week).

The changes are already in master.

cheers,  
shay.banon

---

<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 6, 2017, 4:23am UTC](https://discuss.elastic.co/t/notice-gateway-changes-in-next-version/2968/2 "2017-07-06T04:23:53Z")

</div>

Closed on July 6, 2017, 4:23am UTC