This Week in Elasticsearch - January 29, 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

  • Upgrade to Lucene 4.6.1 (#4897, master, 1.x, 1.0 and 0.90)
  • Ensure rivers _meta documents are retrieved via get with preference _primary (#4864, master, 1.x, 1.0 and 0.90)
  • Reducing pulled in dependencies by marking unused lucene-expressions dep as provided (#4859, master, 1.x, 1.0 and 0.90)
  • Support for multiple rescore operations has been added (#4748, master, 1.x and 1.0)
  • When executing sub aggregations executing on a single shard, the reduce call was not propagated properly down the agg hierarchy (#4843, master, 1.x and 1.0)
  • _site plugins did not pick up on index.html in sub directories (#4845, master, 1.x, 1.0 and 0.90)
  • Removed pre 1.0 transport serialization logic (commit, master, 1.x and 1.0)
  • cat API: Normalize headers, support for pb and tb (#4852, #4871, master, 1.x and 1.0)
  • Dont throttle the translog during recovery (commit, master, 1.x, 1.0 and 0.90)
  • REST mget API: Support for source parameter (#4892, master, 1.x, 1.0 and 0.90)
  • Bulk API: Do not fail the whole request in case the JSON cannot be parsed and special mapping is configured (#4745, master, 1.x, 1.0 and 0.90)
  • REST GET Cluster State: Filtering did not make use of the recently changed parameters correctly (#4885, master, 1.x and 1.0)
  • Percolator response should always return the matches key (#4881, master, 1.x and 1.0)
  • Get Field Mapping API: Behave consistent to other changes when a single field mapping is not found (#4738, master, 1.x and 1.0)
  • REST API: Support for source parameter in percolate mpercolate, msearch and mtermvector APIs (#4900, #4901, #4902, #4903, master, 1.x and 1.0)
  • Cleanup of the Aggregations API (#4922, master, 1.x and 1.0)
  • Hot Threads API: Prevent rare ArrayIndexOutOfBoundsException (#4927, master, 1.x, 1.0 and 0.90)
  • Aggregations: Made REST output consistent over all aggregation types (#4926, master, 1.x and 1.0)

Elasticsearch Ecosystem

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

Slides & Videos


en français: Gérald Croes and Julien Salleyron's Recent Talk from Forum PHP 2013

Where to find Us

We'd love to feature all the great Elasticsearch, Logstash and Kibana presentations and meetups happening worldwide in this section. If you're speaking or hosting a meetup, let our Community Manager, Leslie Hawthorn, know!

Belgium

Czech Republic

Honza Kral will give two presentations at DevConf.cz: 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.

France

Germany

Japan

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.

Sweden

The 4th Stockholm Elasticsearch Meetup has just been scheduled for February 5th. Further details are forthcoming, but you can look forward to presentations from Karel Minařík and Honza Král.

United Kingdom

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.

Trainings

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