Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
1
Description
I think this has gone both directions. We need to nail down what the correct behavior is according to the RFC.
Currently, a MutateIn with StoreSemantics.Upsert does not throw PathAlreadyExists on an XATTR with CreatePath: false, even when the server is returning SubDocPathExists. It just silently succeeds, and there's no way for the user to detect it via any public fields/properties/methods on the return value.
Transactions RFC seems to imply that it should be throwing.
Attachments
Issue Links
For Gerrit Dashboard: NCBC-2831 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
149680,2 | NCBC-2831: MutateIn should throw PathInvalidException when a missing path is used. | master | couchbase-net-client | Status: MERGED | +2 | +1 |
150052,1 | TXNN-69: More FIT failures (dotnet transactions side) | master | couchbase-transactions-dotnet | Status: ABANDONED | -1 | +1 |
150410,3 | NCBC-2831: Classify MutateIn SubDocumentPath errors properly | master | couchbase-net-client | Status: MERGED | +2 | +1 |
150420,5 | TXNN-54: XML documentation for public APIs TXNN-69: More FIT failures (dotnet transactions side) | master | couchbase-transactions-dotnet | Status: MERGED | +2 | +1 |