Versions Compared

Version Old Version 16 New Version 17
Changes made by

Rajesh Kumar

Rajesh Kumar

Saved on

Key

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

Table of Contents

...

#

1idUUID of the event
2source
urn:cps:org.onap.cps
3schema
urn:cps:org.onap.cps:data-updated-event-schema:v1
4type
org.onap.cps.data-updated-delta-event
5content
{
"operation": "UPDATE",
"anchorName": "Anchor1",
"dataspaceName": "dataspace1",
"schemaSetName": "schemaset1",
"observedTimestamp": timestamp,
"data":
Code Block
languagetext
titledata body
collapsetrue
[
  {
    "action": "ADD",
    "xpath": "/bookstore/categories/[@code=3]",
    "payload": {
      "code": 3,
      "name": "kidz"
    }
  },
  {
    "action": "DELETE",
    "xpath": "/bookstore/categories/[@code=1]",
    "payload": {
      "code": 1,
      "name": "Fiction"
    }
  },
  {
    "action": "UPDATE",
    "xpath": "/bookstore/categories/[@code=2]",
    "payload": {
      "name": "Comic"
    }
  }
]
}

...

"subscribeDeltaNotification": true

}

]


Additional field will be added to Anchor table to persist delta notification 

Table Name: AnchorForDeltaNotification

...

notification subscription. newly added field details are as below.  



Updated TableAnchor
new field name notification
typetext
example true (string). change later. 


Open questions to be discussed:

OptiondescriptionDecision

Is it OK to modify Postgres tables instead of using a yang modelled data approach... (this will require Liquibase steps)


TD : Toine Siebelink need to discuss with Architects and update

generic text field OK for future refinement, maybe consider json?



Implementation details

  1. For data nodes update operation, generate delta report by comparing previous and current configuration after successful update. 
  2.  Process data update delta event and send notification as described in event schema above.