# ElasticSearch 1.0 features? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 8, 2013, 5:28pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882 "2013-05-08T17:28:51Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [May 8, 2013, 5:28pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/1 "2013-05-08T17:28:51Z")
Shay commented on an issue about one possible feature in the 1.0 release: > Which leads me to the question: what is in store for 1.0? There are issues tagged v1.0.0.Beta1, so 1.0 is being actively developed. I would love to know the status of some longstanding requests such as: - the referenced facet refactor - full cluster restarts for upgrades ( [https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J](https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J) ) - better backups/export - split brain bug ( [https://github.com/elasticsearch/elasticsearch/issues/2117](https://github.com/elasticsearch/elasticsearch/issues/2117)) Also, when will the 0.20 (last Lucene 3.x) and 0.90 branches stop being worked on? There are a few commits for 0.20.7, which has not been released. Still on 0.20, waiting for 1.0. If there are no relevant features, I might switch to 0.90 instead. Thanks for all the hard work, Ivan -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 8, 2013, 6:11pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/2 "2013-05-08T18:11:08Z")
Re split brain bug ( [split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) Is there a reason why ES doesn't move to ZooKeeper as its default, like SolrCloud did? On Wed, May 8, 2013 at 8:28 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > Shay commented on an issue about one possible feature in the 1.0 release: > [Support Hierarchical Facets · Issue #1076 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1076#issuecomment-17566680) > > Which leads me to the question: what is in store for 1.0? There are issues > tagged v1.0.0.Beta1, so 1.0 is being actively developed. > > I would love to know the status of some longstanding requests such as: > > - the referenced facet refactor > - full cluster restarts for upgrades ( > [Redirecting to Google Groups](https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J) > ) > - better backups/export > - split brain bug ( > [split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) > > Also, when will the 0.20 (last Lucene 3.x) and 0.90 branches stop being > worked on? There are a few commits for 0.20.7, which has not been released. > > Still on 0.20, waiting for 1.0. If there are no relevant features, I might > switch to 0.90 instead. > > Thanks for all the hard work, > > Ivan > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [May 8, 2013, 7:05pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/3 "2013-05-08T19:05:29Z")
There is a plugin to utilize ZooKeeper: > **[GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper)** > > Contribute to sonian/elasticsearch-zookeeper development by creating an account on GitHub. SolrCloud defaults to a single ZooKeeper instance, but in reality you need a ZooKeeper cluster for production installs. I personally do not want to manage another cluster if possible. The only reason why I mentioned the split-brain issue is that since it affects zen discovery, I can envision the solution requiring some substantial (and breaking) changes. If something is going to be re-architected, hopefully it will be in a new version (and not have breaking changes between minor versions). Cheers, Ivan On Wed, May 8, 2013 at 11:11 AM, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com)wrote: > Re split brain bug ( > [split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) > > Is there a reason why ES doesn't move to ZooKeeper as its default, like > SolrCloud did? > > On Wed, May 8, 2013 at 8:28 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > > > Shay commented on an issue about one possible feature in the 1.0 release: > > [Support Hierarchical Facets · Issue #1076 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1076#issuecomment-17566680) > > > > Which leads me to the question: what is in store for 1.0? There are > > issues tagged v1.0.0.Beta1, so 1.0 is being actively developed. > > > > I would love to know the status of some longstanding requests such as: > > > > - the referenced facet refactor > > - full cluster restarts for upgrades ( > > [Redirecting to Google Groups](https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J) > > ) > > - better backups/export > > - split brain bug ( > > [split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) > > > > Also, when will the 0.20 (last Lucene 3.x) and 0.90 branches stop being > > worked on? There are a few commits for 0.20.7, which has not been released. > > > > Still on 0.20, waiting for 1.0. If there are no relevant features, I > > might switch to 0.90 instead. > > > > Thanks for all the hard work, > > > > Ivan > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 8, 2013, 7:10pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/4 "2013-05-08T19:10:38Z")
Zookeeper is overkill. It comes with a load of features. ES is not making use of them. As Igor Motov noted in the elasticsearch-zookeeper plugin, most split-brains happen due to irregular node outages [https://groups.google.com/d/msg/elasticsearch-zookeeper/49V9baDFoZg/J1sOZKSvLwkJ](https://groups.google.com/d/msg/elasticsearch-zookeeper/49V9baDFoZg/J1sOZKSvLwkJ) and Zookeeper can not fix that outages either. On the other hand, there are some leader election algorithms who do not operate with quorums. Hirschberg-Sinclair may be an option, maybe it behaves better in some network disconnection scenarios. Jörg Am 08.05.13 20:11, schrieb Itamar Syn-Hershko: > Re split brain bug > ([split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) > > Is there a reason why ES doesn't move to ZooKeeper as its default, > like SolrCloud did? > > On Wed, May 8, 2013 at 8:28 PM, Ivan Brusic \<[ivan@brusic.com](mailto:ivan@brusic.com) > [mailto:ivan@brusic.com](mailto:ivan@brusic.com)\> wrote: > > ``` > Shay commented on an issue about one possible feature in the 1.0 > release: > https://github.com/elasticsearch/elasticsearch/issues/1076#issuecomment-17566680 > > Which leads me to the question: what is in store for 1.0? There > are issues tagged v1.0.0.Beta1, so 1.0 is being actively developed. > > I would love to know the status of some longstanding requests such as: > * the referenced facet refactor > * full cluster restarts for upgrades > (https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J > ) > * better backups/export > * split brain bug > (https://github.com/elasticsearch/elasticsearch/issues/2117) > > Also, when will the 0.20 (last Lucene 3.x) and 0.90 branches stop > being worked on? There are a few commits for 0.20.7, which has not > been released. > > Still on 0.20, waiting for 1.0. If there are no relevant features, > I might switch to 0.90 instead. > > Thanks for all the hard work, > > Ivan > -- > You received this message because you are subscribed to the Google > Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to elasticsearch+unsubscribe@googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > ``` > > -- > You received this message because you are subscribed to the Google > Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 8, 2013, 7:57pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/5 "2013-05-08T19:57:31Z")
Very early for christmas, but my (never ending) wish list is: - pluggable faceting framework: collations for sorting facet entries, histograms with equidistant and non-equidistant binning (uniform and non-uniform widths), and the longstanding "grouping/collapsing" feature (supervised clustering of docs) - Websockets as an alternative to REST HTTP, together with an event source on node level to pub/sub for ES nodex/index/shard events, and for a streaming API for "piping" JSON into ES bulk indexing - contineous datacenter to datacenter replication (Websockets might help to "tee" an index to multiple targets in the background, without discovery) - query estimator to block "evil"/"heavy" queries from executing - resource watchdog to detect low resource conditions and execute emergency node actions (throttle, admin mail, shutdown) - Lucene DocValues for fast key/value store (should be there already, haven't checked) - classifiers for terms/documents (unsupervised clustering of docs) - improving discovery algorithms (leader election) - lots of tooling OOTB for the lazy admin (web console, backup/restore tool, upgrade tool, hooks for deployment scripts) ... nuff' for ES 2.0, 3.0 and 4.0 if you ask me 🙂 Jörg Am 08.05.13 19:28, schrieb Ivan Brusic: > I would love to know the status of some longstanding requests such as: > > - the referenced facet refactor > - full cluster restarts for upgrades > ([Redirecting to Google Groups](https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J) > [https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J](https://groups.google.com/forum/#%21msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J)) > - better backups/export > - split brain bug > ([split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [May 8, 2013, 8:56pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/6 "2013-05-08T20:56:09Z")
My list is based on previous discussions of issues that could potentially be featured in future releases (1.0). If I had to compile a wish list, mine would be just as long! On Wed, May 8, 2013 at 12:57 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Very early for christmas, but my (never ending) wish list is: > > - pluggable faceting framework: collations for sorting facet entries, > histograms with equidistant and non-equidistant binning (uniform and > non-uniform widths), and the longstanding "grouping/collapsing" feature > (supervised clustering of docs) > > - Websockets as an alternative to REST HTTP, together with an event source > on node level to pub/sub for ES nodex/index/shard events, and for a > streaming API for "piping" JSON into ES bulk indexing > > - contineous datacenter to datacenter replication (Websockets might help > to "tee" an index to multiple targets in the background, without discovery) > > - query estimator to block "evil"/"heavy" queries from executing > > - resource watchdog to detect low resource conditions and execute > emergency node actions (throttle, admin mail, shutdown) > > - Lucene DocValues for fast key/value store (should be there already, > haven't checked) > > - classifiers for terms/documents (unsupervised clustering of docs) > > - improving discovery algorithms (leader election) > > - lots of tooling OOTB for the lazy admin (web console, backup/restore > tool, upgrade tool, hooks for deployment scripts) > > ... nuff' for ES 2.0, 3.0 and 4.0 if you ask me 🙂 > > Jörg > > Am 08.05.13 19:28, schrieb Ivan Brusic: > > > I would love to know the status of some longstanding requests such as: > > > > - the referenced facet refactor > > - full cluster restarts for upgrades ([https://groups.google.com/](https://groups.google.com/)\*\* > > forum/#!msg/elasticsearch/**p2mu0Tv3VPI/0sXdwuwCKR8J[https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J](https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J)\< > > [https://groups.google.com/\*\*forum/#!msg/elasticsearch/](https://groups.google.com/**forum/#%21msg/elasticsearch/)** > > p2mu0Tv3VPI/0sXdwuwCKR8J[https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J](https://groups.google.com/forum/#%21msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J) > > > > > ) > > > > - better backups/export > > - split brain bug ([https://github.com/\*\*elasticsearch/elasticsearch/](https://github.com/**elasticsearch/elasticsearch/)\*\* > > issues/2117 [https://github.com/elasticsearch/elasticsearch/issues/2117](https://github.com/elasticsearch/elasticsearch/issues/2117)) > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscribe@\*\*[googlegroups.com](http://googlegroups.com)[elasticsearch%2Bunsubscribe@googlegroups.com](mailto:elasticsearch%2Bunsubscribe@googlegroups.com) > . > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > . -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![mattweber](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattweber/32/44940_2.png) [@mattweber](https://discuss.elastic.co/u/mattweber)\ **Post date:** [May 8, 2013, 9:41pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/7 "2013-05-08T21:41:26Z")
+1 for basically everything Jorg mentions with an emphasis on the faceting improvements, collapsing/grouping, and dc-to-dc replication. Thanks, Matt Weber On Wed, May 8, 2013 at 1:56 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > My list is based on previous discussions of issues that could potentially be > featured in future releases (1.0). If I had to compile a wish list, mine > would be just as long! > > On Wed, May 8, 2013 at 12:57 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > > > Very early for christmas, but my (never ending) wish list is: > > > > - pluggable faceting framework: collations for sorting facet entries, > > histograms with equidistant and non-equidistant binning (uniform and > > non-uniform widths), and the longstanding "grouping/collapsing" feature > > (supervised clustering of docs) > > > > - Websockets as an alternative to REST HTTP, together with an event source > > on node level to pub/sub for ES nodex/index/shard events, and for a > > streaming API for "piping" JSON into ES bulk indexing > > > > - contineous datacenter to datacenter replication (Websockets might help > > to "tee" an index to multiple targets in the background, without discovery) > > > > - query estimator to block "evil"/"heavy" queries from executing > > > > - resource watchdog to detect low resource conditions and execute > > emergency node actions (throttle, admin mail, shutdown) > > > > - Lucene DocValues for fast key/value store (should be there already, > > haven't checked) > > > > - classifiers for terms/documents (unsupervised clustering of docs) > > > > - improving discovery algorithms (leader election) > > > > - lots of tooling OOTB for the lazy admin (web console, backup/restore > > tool, upgrade tool, hooks for deployment scripts) > > > > ... nuff' for ES 2.0, 3.0 and 4.0 if you ask me 🙂 > > > > Jörg > > > > Am 08.05.13 19:28, schrieb Ivan Brusic: > > > > > I would love to know the status of some longstanding requests such as: > > > > > > - the referenced facet refactor > > > > > > - full cluster restarts for upgrades > > > ([Redirecting to Google Groups](https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J) > > > [https://groups.google.com/forum/#!msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J](https://groups.google.com/forum/#%21msg/elasticsearch/p2mu0Tv3VPI/0sXdwuwCKR8J)) > > > > > > - better backups/export > > > > > > - split brain bug > > > ([split brain condition after second network disconnect - even with minimum\_master\_nodes set · Issue #2117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2117)) > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:37am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-features/11882/8 "2017-07-06T02:37:32Z")