Couchbase Server 2.0.0 build 1495 introduces important changes with respect to accesing views from buckets that have been secure with SASL authentication.
To access a view from a bucket with SASL authentication through the REST API you must supply the bucket name and password as the username and password to the URL of the HTTP request. For example:
Failure to provide the authentication information on a secure bucket will result in an HTTP error response (401).
For more information, see Section 9.8.1, “Querying Using the REST API”.
The same rules also apply to creating and reading design documents using the REST API.
For more information, see Section 9.7, “Design Document REST API”.
Installation and Upgrade
It is not possible to perform an upgrade between Couchbase Server 2.0 pre-releases including beta, or to perform an offline upgrade from Couchbase Server 1.8 to a pre-release or beta of Couchbase Server 2.0. To upgrade between these versions use cbbackup to backup your data, delete the existing installation, install the new version, and restore the stored data.
Documents identified as Non-JSON stored within Couchbase Server may appear as binary, or text-encoded binary data within the UI.
During periods of moderate CPU load on the Couchbase Server
cluster, you may see warnings that
IP address seems to
have changed. Unable to listen to node X.X.X.X.
The cbbackup, cbrestore,
and cbtransfer command-line tools require the
zlib module for Python to have been
installed. If Python was installed from source, you must have
zlib using the
--with-zlib option during the build process.
Indexing and Querying
Accessing a recently created view (with other, existing active views) may return a error if the corresponding design document and view definition have not been replicated across the cluster. The error return will be returned in error of the view output detailing the missing design document. The workaround is to add views and design documents to your node or cluster after you have performed rebalance. For more information about resolving issues with Couchbase Views, see Appendix D, Troubleshooting Views (Technical Background).
Note also that stopping a rebalance operation on a cluster may take a long time if compaction and indexing operations are in progress on the cluster at the point of rebalance. Again, the workaround is to add views and index and query views after you have performed compaction or rebalance. For more information about rebalance, and considerations on when to rebalance, see Section 5.7, “Rebalancing”.