Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
4.6.0
-
None
Description
We have had a few situations with SDKs, views, N1QL where not having a shared representation of CAS when opaque bytes are not possible. For instance, with JSON representation from Views/N1QL/FTS.
This will probably become more important with Timestamp (HLC) Conflict Resolution being added to 4.6, since at least at an observability (or debugging level), people will want this representation.
Assigning to John for now, but I'd be glad to be part of it.