# Upgrade notice when using FS gateway with latest master and upcoming 0.9

**URL:** <https://discuss.elastic.co/t/upgrade-notice-when-using-fs-gateway-with-latest-master-and-upcoming-0-9/3031>\
**Category:** Elasticsearch\
**Created:** [June 21, 2010, 7:44pm UTC](https://discuss.elastic.co/t/upgrade-notice-when-using-fs-gateway-with-latest-master-and-upcoming-0-9/3031 "2010-06-21T19:44:06Z")\
**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:** [June 21, 2010, 7:44pm UTC](https://discuss.elastic.co/t/upgrade-notice-when-using-fs-gateway-with-latest-master-and-upcoming-0-9/3031/1 "2010-06-21T19:44:06Z")

</div>

Hi,

I have just pushed major refactoring to the gateway module. Aside from  
code reuse (there is still work to be done) between different gateway  
implementations, and better scalability when recovering, it is the basis for  
implementing the feature that reuses the work directory content when  
possible. See how to upgrade if you use the FS gateway here:  
[http://github.com/elasticsearch/elasticsearch/issues/#issue/232](http://github.com/elasticsearch/elasticsearch/issues/#issue/232).

-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/upgrade-notice-when-using-fs-gateway-with-latest-master-and-upcoming-0-9/3031/2 "2017-07-06T04:23:07Z")

</div>

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