Today, we are excited to announce the release of Elasticsearch 2.0.0-beta1, based on Lucene 5.2.1. This release contains over 2,500 pull requests from 469 committers. 850 of the pull requests are completely new to 2.0.
IMPORTANT: This is a beta release and is intended for testing purposes only. There is no guarantee that Elasticsearch 2.0.0-beta1 will be compatible with Elasticsearch 2.0.0 GA.
DO NOT DEPLOY IN PRODUCTION
You can download Elasticsearch 2.0.0-beta1 and read the full changes list here.
Elasticsearch 2.0.0-beta1 has some cool new changes like:
- Pipeline Aggregations which allow you to run aggregations on the results of other aggregations, including derivatives, moving averages, and Holt Winters predictive algorithms.
- Better store compression to fit more data into your disks and file system cache.
- Better heap usage with doc-values-by-default, reduced memory usage during merges, and roaring bitsets for filter caching.
- Structured, readable, exceptions.
- Optimised query execution order, auto-caching of filters, and parent-child rewritten for faster queries.
- More reliance on feedback loops instead of settings for auto-regulation.
- Writes to transaction logs are atomic and durable by default.
- A big cleanup to type mappings to make them safe, unambiguous, and reliable.
- Binding only to localhost by default.
- Cluster state diffs for faster change propagation.
Besides the above, there are hundreds of incremental changes in both Elasticsearch and Lucene which make Elasticsearch 2.0 safer, better, and easier. Have a look at these blog posts for more information about this release:
- Elasticsearch 2.0.0.beta1 coming soon!
- The Great Mapping Refactoring
- Store compression in Lucene and Elasticsearch
- Better query execution coming to Elasticsearch 2.0
- Out of this world aggregations
- Staying in Control with Moving Averages - Part 1
- Staying in Control with Moving Averages - Part 2
- The Delete by Query API Is now a plugin
- Elasticsearch unplugged - Networking changes in 2.0
Also see the documentation for Elasticsearch 2.0.0-beta1, and especially the list of breaking changes in 2.0.
We have changed the way we develop our core plugins. These officially supported plugins now reside in the main elasticsearch repository which means that they are tested along with core and are released at the same time as Elasticsearch. Core plugins now have the same version number as Elasticsearch and can be installed as in the following example:
sudo bin/plugin install analysis-icu
The new plugin documentation can be found on our website under the Guide.
Our commercial plugins will also use the same versioning as Elasticsearch and will be released along with Elasticsearch. Shield and Watcher are already available for 2.0.0-beta1 and can be installed as follows:
sudo bin/plugin install license sudo bin/plugin install shield sudo bin/plugin install watcher
There is some exciting news coming about Marvel and Sense, so stay tuned…
The documentation for version 2.0.0-beta1 of the commercial plugins is available here:
We have released the Elasticsearch Migration Plugin to help you check whether you need to upgrade your indices, or take any other action, before trying out Elasticsearch 2.0.0-beta1. It will help you to detect issues like problematic mappings that will no longer work in the upcoming 2.0.0.
You can find the instructions for this plugin on the Elasticsearch Migration repository.
There is a known issue when adding fields of type
ip with the same name to two different mapping types in the same index.This will be fixed in the next release. See #13112 for details.
The more beta testers we have, the sooner we can release Elasticsearch 2.0.0 GA, so please download Elasticsearch 2.0.0-beta1, try it out, and let us know what you think on Twitter (@elastic) or on our forum. You can report any problems on the GitHub issues page.