Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
3.0.x, 4.0
-
*Location*: http://docs.couchbase.com/admin/admin/Views/views-operation.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/600.5.17 (KHTML, like Gecko) Version/8.0.5 Safari/600.5.17
*Referrer*: http://docs.couchbase.com/admin/admin/Views/views-index-updates.html
*Screen Resolution*: 1920 x 1080
*Location*: http://docs.couchbase.com/admin/admin/Views/views-operation.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/600.5.17 (KHTML, like Gecko) Version/8.0.5 Safari/600.5.17 *Referrer*: http://docs.couchbase.com/admin/admin/Views/views-index-updates.html *Screen Resolution*: 1920 x 1080
Description
In this document, it says "Irrespective of the stale parameter, documents can only be indexed by the system once the document has been persisted to disk. If the document has not been persisted to disk, use of the stale will not force this process. You can use the observe operation to monitor when documents are persisted to disk and/or updated in the index."
However, in the "stream-based" view section at http://docs.couchbase.com/admin/admin/Views/views-index-updates.html it would say
"The stale=false view query argument has been enhanced. When an application sends a query that has the stale parameter set to false, the application receives all recent changes to the documents, including changes that haven't yet been persisted to disk. It considers all document changes that have been received at the time the query was received. This means that using the durability requirements or observe feature to block for persistence in application code before issuing the stale=false query is no longer needed."
If the enhancement only applies to stream-based view, then clarification should be needed at both places saying "for stream-based view, observe feature isn't needed, but for regular views, it is." If the enhancement applies to both type of views, stream based or not, then we have a conflict of information here.