Daily Archives: November 7, 2017

2.1.1 & 1.7.0

The Apache CouchDB development community is proud to announce the immediate availability of versions 2.1.1 and 1.7.0 1.7.1 (update: November 11th, 2017).

Both releases are security releases and fix multiple CRITICAL issues. Updates are mandatory.

Due to the severity of the issues and the limited options for workarounds, we will delay the release of detailed descriptions by seven (7) days and publish a full report on Tuesday, November 14th. We expect all CouchDB users to update their installations before then.

We are working with various package managers to ensure a smooth update path, but we can not make any promises. We advise all users to prepare to update from source, instructions can be found in the CouchDB documentation: http://docs.couchdb.org/en/2.1.1/install/index.html (2.1.1) and https://github.com/apache/couchdb/tree/1.7.0/share/doc/src/install (1.7.0 1.7.1).

For download options, see the download section of the main CouchDB website:

http://couchdb.apache.org/#download

Release Details

In addition to the security fix, both releases include a number of additional features and bugfixes.

New features in 2.1.1

  • Support compilation and running under Erlang/OTP 20.x.
  • Improve compaction speed by 10-40%.
  • Improve design doc cache performance.
  • Add support for partial indexes in Mango.
  • Add bookmark pagination to Mango.
  • Add execution_stats option to Mango queries for performance analysis.
  • The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customised via the ini file
  • The current node’s local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.
  • Fauxton now uses a version of React with a BSD license.
  • See the full list here: http://docs.couchdb.org/en/2.1.1/whatsnew/2.1.html

Other Bug Fixes in 2.1.1

  • The couch_peruser functionality is now really fixed. Really.
  • It is now possible to modify shard maps for system databases.
  • Fix issue on macOS with mounted volumes that have a space in their name.
  • 50+ bug fixes and performance improvements, see the full list here: http://docs.couchdb.org/en/2.1.1/whatsnew/2.1.html

Bug fix in 1.7.1 (Update: November 11th, 2017)

New features in 1.7.0

Other Bug Fixes in 1.7.0

CouchDB as a Database Solution

Over the last several months, we’ve been fortunate to have the opportunity to interview a number of CouchDB Developers. A primary question pertained to the top benefits of using CouchDB as a database solution.

The number one slot for the top benefits to using CouchDB as a database solution went to sync. 

PouchDB developer, Nolan Lawson referred to sync as CouchDB’s superpower, going on to state that, “CouchDB isn’t a database; it’s a sync engine.” Developer Joan Touzet calls sync the “killer feature” of CouchDB, sharing that whether you’re doing offline-first client development, running a clustered database or distributing data between various server installations, CouchDB’s master-master replication is better than anything she’s ever used.

Speaking of replication, it didn’t take long to figure out that replication had secured second place in our top benefits list.

Garren Smith mentioned that CouchDB was not just a database you can trust but that CouchDB’s replication, combined with PouchDB, allows developers to build interesting applications that work even when the user is offline. Nick Vatamaniuc mentioned that few databases support the feature of master-to-master replication. He likes that it allows creating custom clustering topologies with various availability and scalability trade-offs.

As for third place? Well, that’s anyone’s guess.

The versatility of the responses speak loud and clear to the gamut of lovable CouchDB features. These include CouchDB’s built-in web interface, its powerful and versatile secondary indexing capabilities, its application data model consistency, support for clustering, schema flexibility and much, much more. Stay tuned to hear more developer details on the benefits of using CouchDB as a database solution.

 

We look forward to digging a bit deeper on some of the benefits mentioned here. If you’d like to add a benefit to our list or there’s something particular you’d like to see covered on the CouchDB blog, we would love to accommodate. Email us!

For more about CouchDB visit couchdb.apache.org or follow us on Twitter at @couchdb.