13 août 2014

This Week in Elasticsearch - August 13, 2014

Par Alexander Reelsen

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

  • Transport: better categorization for transport actions (#7105, master and 1.4)
  • MultiGet & MultiTermVector api: fail when using no routing and an alias to an index that has routing required (#7145, master, 1.4 and 1.3)
  • Core: simultaneous create/delete against same id can cause silently inconsistent replica (#7142, master, 1.4 and 1.3)
  • Percolator: Cache index field data instances (#7081, master, 1.4 and 1.3)
  • Search: add time zone setting for relative date math in range filter/query (#3729, master and 1.4)
  • Aggregations: key_as_string only shown when format specified in terms agg (#7125, master and 1.4)
  • Allocation: Make cluster.routing.allocation.allow_rebalance a dynamic setting (#7092, master and 1.4)
  • CORS: Allowed to configure allow-credentials header to work via SSL (#6380, master and 1.4)
  • Query Cache: Support shard level query response caching (#7161, master and 1.4)
  • Update API: Add support for scripted upserts (#7143, master and 1.4)
  • Java api: Remove operationThreaded setter from ExplainRequestBuilder, already available in base class SingleShardOperationRequestBuilder (#7186, master and 1.4)
  • Internal: Remove (mostly) unused 'failure' member from ShardSearchFailure (#7861, master and 1.4)
  • Mapping API: Improve IP address validation (#7131, master and 1.4)
  • Java API: add index, type and id to ExplainResponse (#7201, master and 1.4)
  • Suggester: Add suggestRequest to Requests and fix broken javadocs in client (#7206, master and 1.4)
  • Internal: removed needless serialization code from TransportIndexReplicationAction and corresponding request object (#7211, master and 1.4)
  • Mapping: fixes dynamic mapping of geo_point fields (#6939, master and 1.4)
  • Internal: Fix a very rare case of corruption in compression used for internal cluster communication (#7210, master, 1.4, 1.3 and 1.2)
  • Core: Pass down the types from the delete mapping request to the delete by query request (#7091, master, 1.4 and 1.3)
  • Core: Avoid null references that may be returned due to concurrent changes or inconsistent cluster state (#7181, master, 1.4 and 1.3)
  • Mappings: Make sure that multi fields are serialized in alphabetic order to ensure that the source is always the same (#7220, master, 1.4, 1.3 and 1.2)
  • Internal: adjusted TermVectorRequest serialization to not serialize and deserialize the index twice (#7221, master and 1.4)
  • Query DSL: Cache range filter on date field by default (#7114, master, 1.4, 1.3 and 1.2)
  • Test: Allow CliTool to write out stacktraces (#7222, master and 1.4)
  • Java client API: CreateIndexRequestBuilder.addMapping throws IllegalStateException if you add same type more than once (#7231, master and 1.4)
  • Core: Store index creation time in index metadata (#7119, master and 1.4)
  • Geo: fixes geo_shapes which intersect dateline (#7016, master and 1.4)
  • Geo: Better error for invalid multipolygon (#7126, master and 1.4)
  • Internal: changed every single index operation to not replace the index within the original request (#7223, master and 1.4)
  • Plugins: bin and config only plugins do not install correctly (#7152, master and 1.4)

Elasticsearch Ecosystem

Here's some more information about what is happening in the ecosystem we are maintaining around the ELK stack - that's Elasticsearch plus Logstash and Kibana - including plugin and driver releases.

Slides & Videos

Are you a Pythonista? Then you are really going to want to watch our resident Python expert Honza Kral in this presentation from the recent PyData Conference in Berlin.

Did Honza's talk not quite satiate your weekly need for all things Python? Don't worry, we've got this special presentation from community member Alex Brasetvik at EuroPython last month that will hopefully do the trick.

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!


If you're heading to FrOSCON on August 23rd & 24th, we're happy to bring you bouncy castle love this year. And make sure to see Isabel Drost-Fromm on Your Search Doesn't Work.

United States

Heading to Chicago for LinuxCon and Cloud Open North America? Say hello to Leslie Hawthorn, and check out her panel Empowering Your Corporate Open Source Software Developers.

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 Elasticsearch, 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:

  • Sao Paulo - August 14, 2014 (core Elasticsearch training)
  • Rio de Janeiro - August 18, 2014 (core Elasticsearch training)
  • New York - August 27, 2014 (ELK workshop)
  • London - September 2, 2014 (core Elasticsearch training)
  • London - September 4, 2014 (ELK workshop)
  • Paris - September 9, 2014 (core Elasticsearch training)
  • Boulder - September 16, 2014 (core Elasticsearch training)
  • Berlin - September 17, 2014 (core Elasticsearch training)
  • Austin - September 18, 2014 (ELK workshop)
  • Paris - September 25, 2014 (ELK workshop)