Description
When using Couchbase Server 5.x, and you get a lock related error, the Status filed is set of "Failure" (-3) and the Exception field is set to null.
You can reproduce with the following code:
var cluster = new Cluster(new ClientConfiguration |
{
|
Servers = new List<Uri> { new Uri("http://10.111.175.101") } |
});
|
|
var authenticator = new PasswordAuthenticator("user", "password"); |
cluster.Authenticate(authenticator);
|
var bucket = cluster.OpenBucket("test"); |
|
dynamic attempt1 = bucket.GetAndLock<dynamic>("12345", TimeSpan.FromSeconds(10)); |
dynamic attempt2 = bucket.GetAndLock<dynamic>("12345", TimeSpan.FromSeconds(10)); |
attempt2 above should be the "bad" result.
Attachments
Issue Links
- relates to
-
NCBC-1500 SDKs must translate LOCKED status code to existing Errors.
- Resolved
For Gerrit Dashboard: NCBC-1679 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
94090,1 | NCBC-1679: Lock related errors not setting Exception and Status fields correctly in the result [WIP] | release25 | couchbase-net-client | Status: ABANDONED | 0 | 0 |
94091,4 | NCBC-1679: Lock related errors not setting Exception and status | master | couchbase-net-client | Status: MERGED | +2 | +1 |
95137,2 | NCBC-1679: Lock related errors not setting Exception and status | release25 | couchbase-net-client | Status: MERGED | +2 | +1 |