This Week in Elasticsearch - January 16, 2014

Welcome to This week in Elasticsearch. In this roundup, we try to inform you about the latest and greatest changes in Elasticsearch. We cover what happened in the GitHub repositories, as well as many Elasticsearch events happening worldwide, and give you a small peek into the future of the project.

Elasticsearch core

  • Elasticsearch 1.0.0.RC1 has been released! We are eager to get your feedback on it, so please try it out and let us know what you think. We also upgraded most of the official plugins already to support elasticsearch 1.0.
  • Elasticsearch 0.90.10 has been released including an important bugfix for thoseusing multiple data paths as well as some geo performance improvements
  • Added internal get index settings API, which is used by the GET /_settings API (#4620, master)
  • Fixed open/close index API when using wildcard only (#4564, master)
  • Add support for flat_settings flag to all REST APIs that output settings (#4140, master)
  • Create standard gc and memory_pool names for JVM stats (#4661, master and 0.90)
  • Added Joda convert to dependencies and shading (#4660, master and 0.90)
  • RestRequest is now an abstract class, and exposes local/remote address (commit, master and 0.90)
  • RestRequest now exposes headers as list (#4609, master and 0.90)
  • ByteSizeUnit now supports terabytes and petabytes (commit, master and 0.90)
  • Added extra REST endpoint for Get settings API (commit, master)
  • Percolate API: Change the sort boolean option to the sort DSL available in search API (#4625, master)
  • Deprecated disable allocation decider (#4488, master)
  • Added action.destructive_requires_name that controls whether wildcard expressions and _all is allowed to be used for destructive operation (#4549, #4481, master)
  • Renamed fuzziness/min_similarity to edit_distance (#4082, master)
  • Deprecated document boost (#4664, master)
  • PageCacheRecycler better reuses memory across threads (#4647, master)
  • Added host name and host address to DiscoveryNode (commit, master and 0.90)
  • Fixed sorting by sub-aggregation in terms agg (#4643, master)
  • Disabling allow_explicit_index breaks bulk (#4668, master and 0.90)
  • Multi data path config can cause a shard to be perceived as corrupted (#4674, master and 0.90)
  • #4681, master and 0.90)
  • Fixed NPE in bool filter, when an empty should filter clause returns a DocIdSet, but null as iterator (#4685, master and 0.90)
  • REST Update Settings API should not take timeout and master_timeout as index parameters (#4692, master and 0.90)
  • Huge geo cleanup, using meters as default unit of measurement, the geo bounding box filter can take arbitrary corners as arguments (#4515, #4084, master)
  • Replaced the multi-field type in favour for the multi fields option that can be set on any core field (#4521, master)
  • Added new option min_doc_count to terms and histogram aggregations (#4662, master)
  • Default stopwords list should be _none_ for all but language-specific analyzers (#4699, master)
  • Renamed `RobinEngine` to LuceneEngine or DefaultEngine (#4633, master)
  • Removed engine.robin.refresh_interval setting (#4706, master)
  • Cat API: Make cat/indices primary shard columns enabled with an HTTP parameter (#4689, master)
  • Make length parameters consistent (#4083, master)
  • Make type wrapping optional for PUT Mapping API request (#4483, master)
  • Added a new coerce flag for numeric field mappings which defaults to true (#4117, master)
  • Tribe Node: The tribes feature allows to create a tribe node that can act as a federated client across multiple clusters (#4708, master)
  • Removed ElasticsearchInterruptedException and handle interrupt state correctly (#4712, master)
  • Don't accept type wrapper in index request by default (#4484, master)
  • Improved support for partial snapshots (#4701, master)
  • Cat API: Use seconds instead of millis for timestamps in cat API (#4696, master)
  • Cat API: Fix cat/allocation diskRatio calculation (#4670, master)
  • Rest APIs: PUT, DELETE and GET consistent for _mapping, _alias, _setting and _warmer (#4071, master )
  • Source filtering: Excluding all fields of an object should not remove parent (#4715, #4047, master)

Elasticsearch Ecosystem

Here's some more information about what is happening in the ecosystem we are maintaining around Elasticsearch, including plugin and driver releases, as well as news about Logstash and Kibana.

Slides & Videos

Loggly at AWS re:Invent 2013 - Infrastructure at Scale: Apache Kafka, Twitter Storm & Elasticsearch

Mastering Elasticsearch with Ruby

Where to find Us


  • Honza Kral will be speaking on What's New in Elasticsearch 1.0 with Aggregations at the Benelux Elasticsearch Meetup in Brussels on Friday, January 31st. Doors open at 6 PM.
  • Leslie Hawthorn and Honza Kral will be attending FOSDEM 2014 on February 1st and 2nd. Stop by the Elasticsearch table to say hello!
  • Leslie Hawthorn will be speaking at the Infrastructure.Next Conference on DevOps: For Happier, More Productive People. Infrastructure.Next takes place on February 5th in Ghent.
  • Czech Republic

    Honza Kral will give two presentations at Design for Cloud with Elasticsearch and Centralized Logging with Logstash. Honza's presentations take place on Friday, February 7th, and the conference runs from the 7th through the 9th.




    Thanks to Jun Ohtani, the 3rd Elasticsearch Meetup will be held in Tokyo on February 7th starting at 7 PM. Please remember to register for the meetup.

    United Kingdom

    Elasticsearch will have two sessions at QCon London, which takes place March 3-7th. You can join Mark Harwood for a tutorial on Using Elasticsearch for Anomaly Detection plus see Shay Banon and Graham Tackley co-present on How Elasticsearch Powers The Guardian's Newsroom. Make sure to stop by our booth to say hello!

    United States

    Where to Find You

    Our Community Manager, Leslie Hawthorn, is hard at work to help folks create more Elasticsearch meetup groups and to help meetup organizers find more speakers. If you are interested in either effort, take a moment to let her know.

    Oh yeah, we're also hiring. If you'd like us to find you for employment purposes, just drop us a note.  We care more about your skill set and passion for Elasticearch, Kibana and Logstash than where you rest your head.


    If you are interested in Elasticsearch training we have courses taught by our core developers coming up in:

    • We're hiring

      Work for a global, distributed team where finding someone like you is just a Zoom meeting away. Flexible work with impact? Development opportunities from the start?