Repository: couchdb-documentation Updated Branches: refs/heads/master cb04aeb66 -> f0a560529
fix build Project: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/repo Commit: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/commit/f0a56052 Tree: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/tree/f0a56052 Diff: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/diff/f0a56052 Branch: refs/heads/master Commit: f0a560529b35830b4bc1d57291a386c88f4b9b6a Parents: cb04aeb Author: Joan Touzet <woh...@apache.org> Authored: Fri Sep 9 08:18:18 2016 -0400 Committer: Joan Touzet <woh...@apache.org> Committed: Fri Sep 9 08:18:18 2016 -0400 ---------------------------------------------------------------------- src/whatsnew/2.0.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/couchdb-documentation/blob/f0a56052/src/whatsnew/2.0.rst ---------------------------------------------------------------------- diff --git a/src/whatsnew/2.0.rst b/src/whatsnew/2.0.rst index 7fac616..9497162 100644 --- a/src/whatsnew/2.0.rst +++ b/src/whatsnew/2.0.rst @@ -45,7 +45,7 @@ Version 2.0.0 nodes will use an optimized Erlang-driven 'internal replication' to ensure data durability and accessibility. Combine a clustered CouchDB with a load balancer (such as ``haproxy``) to scale CouchDB out horizontally. More details - of the clustering feature are available in the :ref:`cluster/index`. + of the clustering feature are available in the :ref:`cluster`. * `Futon` replaced by brand-new, completely re-engineered `Fauxton` interface. URL remains the same. * The new Mango Query Server provides a simple JSON-based way to perform CouchDB @@ -54,7 +54,8 @@ Version 2.0.0 * Rewrites rules of URLs can be performed using JavaScript. * Multiple queries can be made of a view with a single request. * Views can be queried with sorting turned off for a performance boost. -* Database changes feed now takes any valid JSON object for update sequences. +* The update sequences returned by the ``/db/_changes`` feed are no longer just + integers. They can be any JSON value. * Enhanced global changes feed (now resumable/persistent) * New endpoints added (for some, documentation forthcoming):