14 mai 2010 Technique

0.7.0 Released

Par Shay Banon

ElasticSearch version 0.7.0 has just been released. You can download it here. This release brings much improved stability, and several features:

Zen Discovery

A discovery module called zen built from the ground up to work well, and fast with elasticsearch. This is now the default discovery module, with the jgroups discovery module moving to be provided as a plugin.

Groovy Client

A native groovy client providing a Groovyfied API build on top of the native Java API. More details provided in the ElasticSearch Just Got Groovy blog post. As a side note, anybody up for building a Scala/JRbuy client?


First and foremost, native cloud support, providing zero conf cloud discovery ( No Special Node™ ) and the ability to persist long term index storage on different cloud providers blob stores. More information can be found in the Here Comes the Cloud blog post.

Memcached Transport

For that extra oomph when HTTP is not fast enough (mainly from other languages), elasticsearch supports a subset of the memcached protocol. Basically, the implementation implements REST on top of memcached (as much as possible). More info can be found here.

Simpler Plugin Management

Many things in elasticsearch are implemented as a plugin. For example, the cloud support or memcached support are implemented as plugins. Now, installing a plugin is as simple as issuing the following command:

bin/plugin -install cloud
bin/plugin -install transport-memcached

Analysis ICU

Better support when working with unicode through the ICU analysis plugin. More info here.

More APIs

More information on nodes using the new Node stats API, as well as the ability to restart a node.

JVM Clients

Simpler dependency management, requiring only lucene as a dependency.


Though currently mainly for internal use, an abstraction on top of JSON has been created, inspired by JSON called XContent. There is support a JSON implementation for it, but also support for XSON, which is a binary JSON format for faster and smaller (message footprint) messages. The Java API already uses it automatically (not for indexed documents), and both the REST API and the indexed documents can be either in JSON or XSON format. XSON format will be documented in the near future to allow for non JVM based clients to use it.