MutateIn Replace with empty path should not fail

Description

Currently an InvalidArgumentException is raised if a MutateIn replace is performed with an empty path. This should not happen, instead it should set the opcode to SET_DOC and replace the whole document

Relevant RFC section:

A blank path specified for a Replace operation must trigger an sub-document op-code change to LCB_SET as opposed to LCB_SUBDOC_DICT_ADD.

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

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

Details

Assignee

Reporter

Story Points

Sprint

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created September 26, 2023 at 1:12 PM
Updated September 27, 2023 at 8:32 AM
Resolved September 27, 2023 at 8:32 AM
Configure
Instabug