Versions Compared

Key

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

...

draw.io Diagram
bordertrue
diagramNameAnalysis-Async-Schema
simpleViewertrue
width
linksauto
tbstyletop
diagramDisplayName
lboxfalse
diagramWidth951
revision2




#


properties

NCMP Async Headers/

External Props

NCMP Async

has

Forwaded

-Event

NCMP Async

has

Event

DMI Async Headers/

External Props

DMI Async

DMI 

has 

Event-Content

1

eventId

****N/A
2

eventCorrelationId

****N/A
3

eventTime

****N/A
4

eventTarget

****N/A
5

eventType

****N/A
6

eventSchema

****N/A
7

eventSchemaVersion

**N/A*N/A
8

eventSource

N/A***N/A
9

response-data-schema

Event/FE**

Event-Content

*
10

response-status

Event/FE**Event-Content*
11

response-code

Event/FE**Event-Content*
12

forwardedEventData

Fwd Event*N/AN/AN/A
13response-dataEventN/A*Event-Content*


Steps Need to take to update

  • TO check with client that anyone using this schema. If yes, We need to deprecate this version and create the new version.
  • To keep schema consistent map all the properties of 'DMIAsynRequestResponse' to 'NCMPAsynRequestResponse → Event' instead of 'NCMPAsynRequestResponse → ForwardedEvent'.
  • For now 'response-data' of 'DMIAsynRequestResponse' is mapping to 'additional-properties' of 'forwardedEvent' in 'NCMPAsynRequestResponse'
    • 'response-date → payload' should be matched to the 'forwardedEvent → forwardedEventData →forwardedEventPayload ' .
  • If the above mapping is wrong, We need to update the mapping to the appropriate one.
  • If we agreed with team to use 'Event' instead of ' forwardedEvent', We need to introduce the 'schemaVersion' property in 'Event' schema
  • If the above point is agreed, We need to keep only the payload inside the 'Event'.

Conclusion:

  • CPsProp

NOTE: Once we decide all the points, We work on this using Jira '

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1660
'

...