February 2011 Summaries

Elasticsearch 0.15 introduces a versioning feature that enhances document management by assigning a version number to each indexed document, which enables operations like optimistic concurrency control. This allows users to update documents with the assurance that changes are based on the latest version, preventing conflicts when updates attempt to modify stale data. Additionally, the versioning supports a "put if absent" logic by using a create flag, ensuring that documents are not unintentionally overwritten. The feature also provides real-time version information, eliminating the need for explicit refresh calls, and offers informative error messages when conflicts occur, such as when attempting to update or delete non-existent documents. This advancement in versioning integrates seamlessly with Elasticsearch's near real-time capabilities, enhancing both the reliability and efficiency of document indexing and management.

Percolator is a feature in Elasticsearch 0.15 that allows users to register queries against an index and later send documents to identify which queries match them, effectively reversing the traditional search process. Instead of indexing documents and running queries against them, users can register queries and then percolate documents to find matching queries. This feature can be particularly useful for scenarios like monitoring real-time data streams, such as tweets containing specific keywords. Queries are stored as documents in a special _percolator index, which provides persistence and the ability to filter queries using additional criteria. The percolation process leverages all the shards of an index for efficient processing, and the local execution preference enhances performance. Users can also include filtering criteria to narrow down query matches, and increasing the number of replicas can enhance percolation capabilities.