# 0.19.0 Released **URL:** \ **Category:** Elasticsearch\ **Created:** [March 2, 2012, 9:38am UTC](https://discuss.elastic.co/t/0-19-0-released/6864 "2012-03-02T09:38:49Z")\ **Posts on this page:** 11\ **Page:** 1
**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:** [March 2, 2012, 9:38am UTC](https://discuss.elastic.co/t/0-19-0-released/6864/1 "2012-03-02T09:38:49Z")
Hi, ``` 0.19.0 final has just been released. More info here: http://www.elasticsearch.org/blog/2012/03/01/0.19.0-released.html. This release, on top of its features, marks an important improvement to the stability of elasticsearch and includes important bug fixes over 0.18.x, it is highly recommended to upgrade to it. ``` -shay.banon ---
**Author:** ![Michael\_Sick](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Sick](https://discuss.elastic.co/u/Michael_Sick)\ **Post date:** [March 2, 2012, 1:29pm UTC](https://discuss.elastic.co/t/0-19-0-released/6864/2 "2012-03-02T13:29:41Z")
Shay, Just read over the release notes from all the RC's and the final and wanted to say that the pace of delivery is amazing. Thank you for a great product! What are the themes/main features for the .20 release? --Mike On Fri, Mar 2, 2012 at 4:38 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Hi, > > ``` > 0.19.0 final has just been released. More info here: > > ``` > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/2012/03/01/0.19.0-released.html). This > release, on top of its features, marks an important improvement to the > stability of elasticsearch and includes important bug fixes over 0.18.x, it > is highly recommended to upgrade to it. > > -shay.banon ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 2, 2012, 3:51pm UTC](https://discuss.elastic.co/t/0-19-0-released/6864/3 "2012-03-02T15:51:09Z")
Facets memory optimization as Shay wrote before. David 😉 @dadoonet Le 2 mars 2012 à 14:29, Michael Sick [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com) a écrit : > Shay, > > Just read over the release notes from all the RC's and the final and wanted to say that the pace of delivery is amazing. Thank you for a great product! > > What are the themes/main features for the .20 release? > > --Mike > > On Fri, Mar 2, 2012 at 4:38 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Hi, > > ``` > 0.19.0 final has just been released. More info here: http://www.elasticsearch.org/blog/2012/03/01/0.19.0-released.html. This release, on top of its features, marks an important improvement to the stability of elasticsearch and includes important bug fixes over 0.18.x, it is highly recommended to upgrade to it. > > ``` > > -shay.banon ---
**Author:** ![Michael\_Sick](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Sick](https://discuss.elastic.co/u/Michael_Sick)\ **Post date:** [March 2, 2012, 4:16pm UTC](https://discuss.elastic.co/t/0-19-0-released/6864/4 "2012-03-02T16:16:02Z")
Thanks David - perhaps my memory needs optimization. I was more curious though if there's a running list of features/bugs that were being planned for the release. On Fri, Mar 2, 2012 at 10:51 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > Facets memory optimization as Shay wrote before. > > David 😉 > @dadoonet > > Le 2 mars 2012 à 14:29, Michael Sick [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com) a > écrit : > > Shay, > > Just read over the release notes from all the RC's and the final and > wanted to say that the pace of delivery is amazing. Thank you for a great > product! > > What are the themes/main features for the .20 release? > > --Mike > > On Fri, Mar 2, 2012 at 4:38 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > Hi, > > > > ``` > > 0.19.0 final has just been released. More info here: > > > > ``` > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/2012/03/01/0.19.0-released.html). This > > release, on top of its features, marks an important improvement to the > > stability of elasticsearch and includes important bug fixes over 0.18.x, it > > is highly recommended to upgrade to it. > > > > -shay.banon ---
**Author:** ![Eric\_Jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eric_jain/32/834_2.png) [@Eric\_Jain](https://discuss.elastic.co/u/Eric_Jain)\ **Post date:** [March 3, 2012, 1:46am UTC](https://discuss.elastic.co/t/0-19-0-released/6864/5 "2012-03-03T01:46:49Z")
On Mar 2, 1:38 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > ``` > 0.19.0 final has just been released. More info here:http://www.elasticsearch.org/blog/2012/03/01/0.19.0-released.html. This release, on top of its features, marks an important improvement to the stability of elasticsearch and includes important bug fixes over 0.18.x, it is highly recommended to upgrade to it. > > ``` Thanks, this project is amazing! ---
**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:** [March 3, 2012, 10:07pm UTC](https://discuss.elastic.co/t/0-19-0-released/6864/6 "2012-03-03T22:07:36Z")
The major changes for the next few weeks on 0.20 that I was planning to try and tackle (hopefully successfully 🙂 ) are: - Better shard allocation, initially trying to even out shard allocation also based on which index they belong to, to get even distribution also within an index across a cluster. - Refactor the field data support, allowing for different pluggable implementations, which can allow for ones that are more optimized for memory usage for example. It will tie in with the mapping allowing to decide which one to use on which field, though the aim is to have sensible auto detected defaults. - Refactor the search execution code, to allow for more interesting search executions, like one that does grouping. Once its done, try and see if we can tackle grouping. On Friday, March 2, 2012 at 3:29 PM, Michael Sick wrote: > Shay, > > Just read over the release notes from all the RC's and the final and wanted to say that the pace of delivery is amazing. Thank you for a great product! > > What are the themes/main features for the .20 release? > > --Mike > > On Fri, Mar 2, 2012 at 4:38 AM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com) ([mailto:kimchy@gmail.com](mailto:kimchy@gmail.com))\> wrote: > > > Hi, > > > > ``` > > 0.19.0 final has just been released. More info here: http://www.elasticsearch.org/blog/2012/03/01/0.19.0-released.html. This release, on top of its features, marks an important improvement to the stability of elasticsearch and includes important bug fixes over 0.18.x, it is highly recommended to upgrade to it. > > > > ``` > > > > -shay.banon ---
**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:** [March 4, 2012, 8:15am UTC](https://discuss.elastic.co/t/0-19-0-released/6864/7 "2012-03-04T08:15:30Z")
Heya > - Better shard allocation, initially trying to even out shard > allocation also based on which index they belong to, to get even > distribution also within an index across a cluster. > - Refactor the field data support, allowing for different pluggable > implementations, which can allow for ones that are more optimized for > memory usage for example. It will tie in with the mapping allowing to > decide which one to use on which field, though the aim is to have > sensible auto detected defaults. > - Refactor the search execution code, to allow for more interesting > search executions, like one that does grouping. Once its done, try and > see if we can tackle grouping. All the above sound excellent. I think you probably have this planned for another version, but a feature I'd love to see is: more visibility of nested docs. For instance: - which of my 10 nested Comments caused this Blog to match my query? - with highlighting per nested doc - sorting by a field in a matching nested doc > clint ---
**Author:** ![Mark\_Waddle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_waddle/32/2608_2.png) [@Mark\_Waddle](https://discuss.elastic.co/u/Mark_Waddle)\ **Post date:** [March 5, 2012, 7:01am UTC](https://discuss.elastic.co/t/0-19-0-released/6864/8 "2012-03-05T07:01:55Z")
I agree, all of those changes are great. I am especially excited about the potential for grouping! @Clinton: I am not sure how the sorting on a nested document field would work. If you have multiple nested documents, then it could hit on multiple nested documents, and then it would not be clear as to which to sort on. If there is only one nested document per root document, then you could have a copy of the sort field on the root document. On Sunday, March 4, 2012 12:15:30 AM UTC-8, Clinton Gormley wrote: > Heya > > > - Better shard allocation, initially trying to even out shard > > allocation also based on which index they belong to, to get even > > distribution also within an index across a cluster. > > - Refactor the field data support, allowing for different pluggable > > implementations, which can allow for ones that are more optimized for > > memory usage for example. It will tie in with the mapping allowing to > > decide which one to use on which field, though the aim is to have > > sensible auto detected defaults. > > - Refactor the search execution code, to allow for more interesting > > search executions, like one that does grouping. Once its done, try and > > see if we can tackle grouping. > > All the above sound excellent. > > I think you probably have this planned for another version, but a > feature I'd love to see is: more visibility of nested docs. > > For instance: > > - which of my 10 nested Comments caused this Blog to match my query? > - with highlighting per nested doc > - sorting by a field in a matching nested doc > > > > > clint ---
**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:** [March 5, 2012, 9:51am UTC](https://discuss.elastic.co/t/0-19-0-released/6864/9 "2012-03-05T09:51:35Z")
On Sun, 2012-03-04 at 23:01 -0800, Mark Waddle wrote: > I agree, all of those changes are great. I am especially excited about > the potential for grouping! > > @Clinton: I am not sure how the sorting on a nested document field > would work. If you have multiple nested documents, then it could hit > on multiple nested documents, and then it would not be clear as to > which to sort on. If there is only one nested document per root > document, then you could have a copy of the sort field on the root > document. You could choose to sort on the best matching nested doc, for instance. clint > On Sunday, March 4, 2012 12:15:30 AM UTC-8, Clinton Gormley wrote: > Heya > > ``` > > - Better shard allocation, initially trying to even out > shard > > allocation also based on which index they belong to, to get > even > > distribution also within an index across a cluster. > > - Refactor the field data support, allowing for different > pluggable > > implementations, which can allow for ones that are more > optimized for > > memory usage for example. It will tie in with the mapping > allowing to > > decide which one to use on which field, though the aim is to > have > > sensible auto detected defaults. > > - Refactor the search execution code, to allow for more > interesting > > search executions, like one that does grouping. Once its > done, try and > > see if we can tackle grouping. > > All the above sound excellent. > > I think you probably have this planned for another version, > but a > feature I'd love to see is: more visibility of nested docs. > > For instance: > - which of my 10 nested Comments caused this Blog to match my > query? > - with highlighting per nested doc > - sorting by a field in a matching nested doc > > > clint > > ``` ---
**Author:** ![Eric\_Jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eric_jain/32/834_2.png) [@Eric\_Jain](https://discuss.elastic.co/u/Eric_Jain)\ **Post date:** [March 5, 2012, 6:26pm UTC](https://discuss.elastic.co/t/0-19-0-released/6864/10 "2012-03-05T18:26:30Z")
On Mar 4, 12:15 am, Clinton Gormley [cl...@traveljury.com](mailto:cl...@traveljury.com) wrote: > I think you probably have this planned for another version, but a > feature I'd love to see is [...] ...more elasticity! ---
**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, 3:37am UTC](https://discuss.elastic.co/t/0-19-0-released/6864/11 "2017-07-06T03:37:17Z")