Changes

We use Elastic in production for more since 2012. Although Elastic is quite stable from our experience, we don't have a stable API, and probably never will.

The reason for this is that Elasticsearch changes quite often and at a fast pace. At this moment we still focus on features, not on a stable API.

Having said that, there have been no huge changes that required us to rewrite our applications big time. More often than not it's renaming APIs and adding/removing features so that we are in sync with the Elasticsearch API.

This page is meant to be a guideline about changes in the API as we move along from version to version.

Upcoming changes

The client-refactoring branch will come up with a lot of changes, most of them internally.

• It will automatically pick up changes in your cluster (adding/removing nodes).
• It will use all your nodes by a round-robin strategy.
• It will automatically detect dead nodes and revive dead nodes.
• It will automatically retry requests up to a configured retry count.
• It will have a separating between logging and tracing (Debug(...) in services is gone).
• It will allow you to use your own decoder for the JSON response.
• It will have some more APIs.