Versions Compared

Old Version 9

changes.mady.by.user Arpit Singh

Saved on

compared with

New Version 10

changes.mady.by.user Arpit Singh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Overview

The second API proposed under the Delta feature is to generate a delta between configuration stored under an Anchor and JSON payload provided by the user. All the responses and exceptions thrown by this API will be similar to the API to generate delta between 2 anchors to maintain consistency between the API's.

...

Pros and Cons of each workaround

WorkaroundProsConsNotes
Limiting the delta between Anchor and JSON payload to only one DataNodeThe DeltaReport will be consistent with the existing API i.e., Delta between 2 anchors
  • Limited to only 1 data node at a time


Using alternative paths, like JSON pathThe delta report will have xpaths replaced by JSON path
  • CPS is dependent and built around xpath, hence this will be a major inconsistency
  • If implemented, we will need to generate JSON paths for both, the data from anchor and the JSON payload,
  • making the operation more expensive

Not reporting the xpaths in the delta report between anchor and JSON payloadCan be implemented for multiple data nodes
  • Delta report will be inconsistent and not as per the RFC standard
  • It is inconsistent with respect to the existing API of delta report.

Mechanism for Delta generation between Anchor and Payload