Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

MutateIn is not throwing and classifying sub-doc errors correctly.

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.

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

Richard Ponton March 25, 2021 at 11:04 PM

It seems we are swallowing SubDocMultiPathFailure.

 

                    if (status == ResponseStatus.SubDocMultiPathFailure)
                    {
                        return;
                    }

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 2, 2021 at 12:00 AM
Updated April 7, 2021 at 4:58 PM
Resolved April 7, 2021 at 4:58 PM
Instabug