http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/JCBC-143 Couchbase Java Client Hopefully this is just a doc bug and not in the actual code, but all of the atomic updates including prepend (<a href="http://www.couchbase.com/docs/couchbase-sdk-java-1.0/couchbase-sdk-java-update-prepend.html">http://www.couchbase.com/docs/couchbase-sdk-java-1.0/couchbase-sdk-java-update-prepend.html</a>) should not require CAS. That significantly defeats their performance effectiveness. <br/> <br/> If the function *does* require CAS, we should document that a CAS id of 0 will override the requirement to get the key again as in this example: <br/> client.prepend(casv.getCas(),&quot;samplekey&quot;, &quot;prependedstring&quot;); <br/> JCBC-143

Prepend should not require CAS

Bug Major Resolved Duplicate Public Michael Nitschinger Perry Krug Thu, 8 Nov 2012 08:18:29 -0600 Fri, 21 Dec 2012 02:28:52 -0600 Fri, 21 Dec 2012 02:28:52 -0600 1.0.3 1.1.1 docs 0 0 This is not a doc bug, both prepend and append require CAS values. <br/> <br/> So is this still a doc enhancement or should we consider enhancing the library? I think a simple doc enhancement to inform the user that they can replace the actual CAS call with a 0 to avoid the second round-trip to the server. There are a few situations where CAS would be appropriate for these ops, so it doesn&#39;t make sense to remove it from the library, but the most common case is to use them as atomic operations and therefore not need CAS...so the doc update should just make that clearer. Please make sure to note it on the various other atomic ops (incr/dev/append/touch/) This is a duplicate for <a href="http://www.couchbase.com/issues/browse/JCBC-196" title="append/incr/decr/add/replace should not require CAS value to be passed">JCBC-196</a>, see the process over there. Duplicate JCBC-196 Rank 9493 Time In Status