11 Dezember 2013

This Week in Elasticsearch - December 11, 2013

Von 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. Also, do not miss our Introduction to logstash webinar tomorrow!

Elasticsearch core

  • has_child query can yield in wrong results if parent type has nested inner objects (#4341, 0.90 and master)
  • Fix _all boosting, which did not work correctly under certain conditions (#4315, 0.90 and master)
  • Allow to disable sending a refresh-mapping to master node, using the indices.cluster.send_refresh_mapping setting (#4342, 0.90 and master)
  • FsStats: Added a total section, that sums up infos for all data paths (#4343, 0.90 and master)
  • FsStats: Added IO operation information, which sums op reads and writes (#4344, 0.90 and master)
  • Fixed inconsistent proximity search results (#4356, 0.90 and master)
  • Improve processing time for indices with large updates of mappings (#4373, 0.90 and master)
  • CpuStats: Add a new usage metric (#4374, 0.90 and master)
  • Support YAML as output format of the analyze API (#4311, master only)
  • Query String caching could cause matched_filters not working (#4361, 0.90 and master)
  • Support postings highlighter in percolate API (#4385, 0.90 and master)
  • The BalancedShardsAllocator accidentally overwrote some of its own set variables in specific cases (#4390, 0.90 and master)
  • Remove term_index_interval and term_index_divisor settings (#3912, 0.90 and master)
  • Fix bug in explain for function_score queries. (commit, 0.90 and master)
  • A search preference for an unknown node returns a client error now (commit, 0.90 and master)
  • Introduce BytesTransportRequest, which allows to share request bodies for several requests instead of allocating new objects (like in the cluster state) (commit, 0.90 and master)
  • Wildcard support to field resolving in Get Field Mapping API (#4367, 0.90 and master)
  • Packaging: Ensure setting of sysctl vm.max_map_count (#4397, 0.90 and master)
  • Geodistance calculations now make use of the faster SloppyMathUtils (#3862, 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.


Where to find Us


David Pilato will speak at the Tours Java Users' Group on December 11th. David's talk will cover all things Elasticsearch, including new features in 1.0. Doors open at 7:15 PM.


The first ever Elasticsearch Tel Aviv meetup will take place on December 30th, beginning at 7 PM. Join Elasticsearch core developer Uri Boness, who will present on what's new in Elasticsearch 1.0, and Itamar Syn-Hershko, who will discuss Monitoring online conversation at scale using Elasticsearch.


Boaz Leskes will talk about Elasticsearch at 010dev in Rotterdam at the 9th of January.

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: