We're constantly tracking, building and testing the latest releases of databases to run on the Compose platform. When they are ready, we add them to the Settings/Version selector in your dashboard for you to seamlessly migrate when you are ready. Of course, you need to know these new versions are around, and that's one of the reasons we do these Support Desk posts.
Elasticsearch 1.4.1: The latest version of Elasticsearch, 1.4.1, is now available on Compose. Version 1.4 is all about resilience and stability so most of the changes are under the hood. There are some useful new features in 1.4 such as the circuitbreaker for requests which can stop excessive use of memory in a query and some new aggregation functions. See this Elasticsearch blog post for a summary of the changes.
Version 1.4.1 builds on that with improvements to disk sharding, handling parent/child and nested documents better and fixing some outstanding timestamp issues. See this blog post for details of those fixes.
New deployments of Elasticsearch will use version 1.4.1 as it's the current stable version. For existing deployments, they can be upgraded to 1.4.1 or continue using the 1.3 branch but if so, read on...
Elasticsearch 1.3.6: If you are happy with your current Elasticsearch 1.3 installation, then there's Elasticsearch 1.3.6 available as an upgrade for you. It's all bug fixes according to the release notes and is a simple upgrade for any Elasticsearch deployment on Compose.
Redis 2.8.18: This is a low priority update with some non-critical bug fixes and a number of new features. The Redis release notes for 2.8 lists them. The biggest feature, diskless replication, is still officially experimental and so isn't being activated on Compose deployments. Other changes include bandwidth tracking in INFO and improved Lua scripting. If you build your own
redis-cli executable to connect with Redis you may want to update it to the version from Redis 2.8.18 as some terminal issues have been cleared up along with a long-standing long timeout connect bug where the client would just quit. This means there's no rush to update for existing installs but new deployments will use the newest version.
The League of Versions
To keep track of all current available versions, we are introducing our League of Versions table. This'll be updated as we roll out new versions or change defaults. Generally, we support upgrades only - contact firstname.lastname@example.org if you need advice of any other version change.
|Database||Available Versions||Default Version|
|Elasticsearch||1.1.1, 1.2.1, 1.3.2, 1.3.4, 1.3.5, 1.3.6, 1.4.1||1.4.1|