Elasticsearch 1.0 has launched!

Big congratulations to the Elasticsearch team, which shipped its version 1.0 yesterday! This is a major milestone that represents thousands of hours of effort from a team with a ton of momentum.

We’re also pleased to announce that you can now use Elasticsearch 1.0 on Bonsai! As of yesterday, all new Heroku Add-on accounts in US East are being provisioned on Elasticsearch 1.0.

<pre><code>{   "status": 200,   "name": "Crimson Dynamo",   "version": {     "number": "1.0.0"   },   "tagline": "You Know, for Search" } </code></pre>

Upgrade Plans for Existing Customers

Because Elasticsearch 1.0 is a major release, it also introduces a number of backwards-incompatible changes to its APIs. That means we need to be careful to allow plenty of time for our customers to test their applications against the newer APIs and fix any changes that need to be made.

Our first step toward 1.0 will be to upgrade our clusters to the very latest version of the Elasticsearch 0.90 series (currently 0.90.11). We’ll perform that upgrade next week, on Wednesday, February 19th. This upgrade will include an upgrade to Lucene, and a number of other changes and fixes that should help ease the transition to 1.0 on the back end.

We’ll keep a close eye on our new 1.0 cluster, as well as on Elasticsearch development activities, in order to spot any last-minute bug fixes that may necessitate a bug-fix 1.0.1 release. Assuming all goes smoothly, we will perform the final upgrade to Elasticsearch 1.0 on Wednesday, March 12th. That is in one month from today.

Timeline

• Wednesday, February 12th
• Elasticsearch 1.0 release
• All new Bonsai clusters in US East are created on Elasticsearch 1.0

• Wednesday, February 19th
• Bonsai 0.90 clusters are upgraded to the latest 0.90 series
• Wednesday, March 12
• All Bonsai 0.90 clusters are upgraded to Elasticsearch 1.0

Preparing For Elasticsearch 1.0

First off, you should download and install Elasticsearch 1.0. Set it up in your local development environment, and test your application accordingly.Next, Heroku users can create a new Bonsai Add-on account to be provisioned on our 1.0 cluster. Using heroku fork makes it trivial to create a full copy of your production environment, at which point you can reindex and use the app to verify that all is well in production.If you’re willing to reindex, and would like to move over sooner, you can email us at support@bonsai.io and we can migrate you right away. Otherwise, stay tuned for the in-place upgrade in March.