This Week in Elasticsearch - July 24, 2013
Welcome to the fourth issue of This week in elasticsearch. In this format we try to inform you about the latest and greatest changes in elasticsearch. We try to cover what happened in the github repositories, as well as all the events happening about elasticsearch and give you a small peek in the future.
- The new distributed and thus far more scalable percolator has landed in master (now also including statistics) (#3173)
- The has_child query has been optimized with two possible shortcuts (#3190, master and 0.90)
- The Thai analyzer now supports stopwords (#3342, master and 0.90)
- Field data now supports more than 2 billion unique ordinals per segment, and memory usage of multi-ordinal data structures has been improved, (#3189, master and 0.90)
- Transport layer now has a dedicated channel for pings in order to make sure, that pings in the cluster can always be sent. A huge cluster state update could block a ping until now (#3362, master and 0.90)
- Missing filter now works the same in top-level and all other filters (#3356, master and 0.90)
- Pattern char replace filter now handles empty replacement setting (#3359, master and 0.90)
- Zen Discovery cluster events and reroute post shards now have an URGENT priority (#3361 and this commit, master and 0.90)
- Proper validation of add aliases requests (#3363)
- Often master node actions are changing the cluster state. As it does not make any sense to block the management thread pool, the cluster service now works using actions, which also allows to define timeouts (using the master_node_timeout configuration setting). (#3365, master and 0.90). In addition an API to see pending cluster tasks has been added (#3368, in master and 0.90)
- Highlighting for complex queries (such as multi phrase) is now supported. These changes will also be part of Lucene 4.5 (#3357, master and 0.90)
- Large response processing could lead to slower search performance as following requests had to clean up filled up resources (#3322, master and 0.90, however solved differently in 0.90)
- Optimizing now got a dedicated thread pool now. This allows to run several optimize calls in parallel on one node, if you have powerful machines (#3366, in master and 0.90)
- Upgraded to Lucene 4.4 (master and 0.90)
- Preparing for netty 4 by removing cached stream output (master and 0.90)
- Bulking of update mapping cluster events, so cluster state changes become less frequent (master and 0.90)
- FuzzyLikeThisFieldQueryBuilder and REST API had different defaults (#3374, master and 0.90)
- There is currently work going on for a new suggester, which is doing prefix suggestions. Please check out the github issue and comment, we are eager to get your feedback there!
We try to give you some more information about what is happening in the ecosystem we are maintaining around elasticsearch, be it plugin or driver releases or news about kibana.
- A first version of GCE cloud plugin has been released. This plugin uses the GCI API for discovery, similar as the amazon plugin does for AWS. We are happy to get any feedback for this plugin.
Got an interesting open source project, plugin, driver or anything else for elasticsearch? Here is your time to shine! Just drop us a note and we will list it here (and on the .org website, of course!).
- An interesting blog post about using fluent with elasticsearch and kibana
- A small blog post about running elasticsearch within stackato
- Sense 0.7 - a useful plugin for Google Chrome - has been released
- Python client pyelasticsearch 0.6 has been released
- The nodejs module elastic-client has been released in version 0.0.3 - In addition to executing queries you can also manage, start and stop elasticsearch instances.
- We will be present at the Open Source Convention (OSCON) in Portland on July 22nd to 26th. Come by and visit us! Kevin Kluge will be introducing Apache Cloudstack and Clinton Gormley will show how to use Moose and Elastic::Model to store your data in Elasticsearch.
- Simon Willnauer will speak at Berlin Tech Openair next week about real-time search and analytics.
- The Elasticsearch Usergroup Berlin is meeting next Tuesday. Stand up and propose a talk if you have something interesting about elasticsearch.
Also, if you are interested in a core elasticsearch training, the next locations are San Francisco (limited offer: get three seats for the price of two!) and Boston at the beginning of August. For more locations, check the training page.
If you are interested in all this, we are hiring. We are interested in your skills, not in your location. Just drop us a note.