gNMI Set Semantics when Update and Replace fields intersect

[wenovus]

Hi,

message SetRequest {
...
  repeated Update replace = 3;    // Updates specifying elements to be replaced.
  repeated Update update = 4;     // Updates specifying elements to updated.
...
}

From the surface of this definition it looks to me that it's possible for the updates to intersect. Is this right? If so, how should this be handled?

[wenovus]

Nevermind, this is addressed in the spec here: https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#34-modifying-state.