# ElasticSearch 0.14 Released

**URL:** https://discuss.elastic.co/t/elasticsearch-0-14-released/3703
**Category:** Elasticsearch
**Created:** [December 28, 2010, 9:58am UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703 "2010-12-28T09:58:01Z")
**Posts on this page:** 7
**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: [December 28, 2010, 9:58am UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/1 "2010-12-28T09:58:01Z")

</div>

Hi,

ElasticSearch 0.14 released, see more here:  
[http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html](http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html).

cheers,  
-shay.banon

---

<div class="post-metadata">

### Author: ![medcl\_net](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@medcl\_net](https://discuss.elastic.co/u/medcl_net)
#### Post date: [December 28, 2010, 10:04am UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/2 "2010-12-28T10:04:33Z")

</div>

cool~~~  
From: Shay Banon  
Sent: Tuesday, December 28, 2010 5:58 PM  
To: users  
Subject: ElasticSearch 0.14 Released

Hi,

ElasticSearch 0.14 released, see more here: [http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html](http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html).

cheers,  
-shay.banon

---

<div class="post-metadata">

### Author: ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)
#### Post date: [December 28, 2010, 5:16pm UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/3 "2010-12-28T17:16:53Z")

</div>

Awesome! \_source highlighting is going to save us buying some hard  
disks 🙂

One thing that I am never 100% clear on, what is the correct upgrade  
path? In our case, we're doing a full rebuild to get rid of some  
stored highlight fields, so it is a moot point, but am curious anyways  
and think this should be a dedicated section in the release notes.

Thanks for all the great work!!!

On Dec 28, 3:04 am, [medcl2...@gmail.com](mailto:medcl2...@gmail.com) wrote:

> cool~~~  
> From: Shay Banon  
> Sent: Tuesday, December 28, 2010 5:58 PM  
> To: users  
> Subject: Elasticsearch 0.14 Released
> 
> Hi,
> 
> Elasticsearch 0.14 released, see more here:[http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html](http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html).
> 
> cheers,  
> -shay.banon

---

<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: [December 28, 2010, 6:17pm UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/4 "2010-12-28T18:17:41Z")

</div>

0.14 upgrade requires a full cluster restart, and make sure to upgrade the  
clients as well if using the Java API. There is no need to rebuild indices.

Its a good point that it should be listed in any release notes. In general,  
when there is a need to reindex data, it is listed in the release notes /  
release announcement, if not, then the upgrade path between major versions  
is the one listed above.

-shay.banon

On Tue, Dec 28, 2010 at 7:16 PM, Paul [ppearcy@gmail.com](mailto:ppearcy@gmail.com) wrote:

> Awesome! \_source highlighting is going to save us buying some hard  
> disks 🙂
> 
> One thing that I am never 100% clear on, what is the correct upgrade  
> path? In our case, we're doing a full rebuild to get rid of some  
> stored highlight fields, so it is a moot point, but am curious anyways  
> and think this should be a dedicated section in the release notes.
> 
> Thanks for all the great work!!!
> 
> On Dec 28, 3:04 am, [medcl2...@gmail.com](mailto:medcl2...@gmail.com) wrote:
> 
> > cool~~~  
> > From: Shay Banon  
> > Sent: Tuesday, December 28, 2010 5:58 PM  
> > To: users  
> > Subject: Elasticsearch 0.14 Released
> > 
> > Hi,
> > 
> > Elasticsearch 0.14 released, see more here:  
> > [http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html](http://www.elasticsearch.com/blog/2010/12/27/0.14.0-released.html).
> > 
> > cheers,  
> > -shay.banon

---

<div class="post-metadata">

### Author: ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)
#### Post date: [December 28, 2010, 6:22pm UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/5 "2010-12-28T18:22:22Z")

</div>

On Tue, 2010-12-28 at 20:17 +0200, Shay Banon wrote:

> 0.14 upgrade requires a full cluster restart, and make sure to upgrade  
> the clients as well if using the Java API. There is no need to rebuild  
> indices.

A full cluster restart as in all nodes must be shut down at the same  
time, or each node can be restarted one at a time?

clint

---

<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: [December 28, 2010, 6:23pm UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/6 "2010-12-28T18:23:35Z")

</div>

Sorry, should have been more specific, full cluster shutdown and then  
restart.

On Tue, Dec 28, 2010 at 8:22 PM, Clinton Gormley [clinton@iannounce.co.uk](mailto:clinton@iannounce.co.uk)wrote:

> On Tue, 2010-12-28 at 20:17 +0200, Shay Banon wrote:
> 
> > 0.14 upgrade requires a full cluster restart, and make sure to upgrade  
> > the clients as well if using the Java API. There is no need to rebuild  
> > indices.
> 
> A full cluster restart as in all nodes must be shut down at the same  
> time, or each node can be restarted one at a time?
> 
> clint

---

<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:14am UTC](https://discuss.elastic.co/t/elasticsearch-0-14-released/3703/7 "2017-07-06T04:14:46Z")

</div>


