-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to save document edited during ChangeTracking #174
Comments
I believe that for inserting a document I was treating KeyExists as a consistency error to catch cases where you're inserting a new document and that document already exists. Is the SDK also returning KeyExists for updates to existing documents? |
I would have expected it to be "Success" |
On my machine this test is currently passing.
Brant |
My cluster is two 4.5.1-2844 Enterprise Edition (build-2844) nodes. I'll check to see if I get the same on 4.6.0. |
Hmm, the test also passes for me when using 4.6.0-3558 Enterprise Edition (build-3558). @jeffrymorris @brantburnett Can one of you verify if you see this test fail with server 4.5.1 please? It may be a 4.5.1 server bug. |
@MikeGoldsmith @brantburnett - i have a 4.5.1 cluster I can test against. |
@jeffrymorris have you had any luck reproducing this bug? |
This integration test fails:
BucketContextTests.SubmitChanges_WhenDocsAreModified_DocumentIsMutated
with the error:
Couchbase.Linq.CouchbaseConsistencyException : Data exists for key
The test enables ChangeTracking, retrieves and updates a document then calls SubmitChanges(). This should update the stored document, but is instead throwing CouchbaseConsistencyException which indicates the result's status was "KeyExists". See here.
I don't think a KeyExists response code should be interpreted as consistency issue.
The text was updated successfully, but these errors were encountered: