According to my notes…
In order for the timestamp in the CAS to be reliable, the bucket must have been created by Couchbase Server 4.6 or later, and the document change must have been performed by Couchbase Server 7.0 or later. Even then, it’s possible for a
set_with_meta
operation to assign an arbitrary CAS value (and therefore timestamp) to a document.
Also, yes, end-users should treat the CAS an opaque.
Thanks,
David