...
# | Description | Notes | Decision | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | No Event properties defined for DMI AVC Event | Priyank Maheshwari will need to specify and agreed event structure for DMI AVC Event with stakeholders ie. provide Jira ticket | Event Body should be compatible with RFC8641 kieran mccarthy to confirm. Priyank Maheshwari to create JIRA to create the event body schema. | ||||||||
2 | Bulk Operation events details have not yet be defined (just headers) | Sourabh Sourabh to provide Jira tickets |
| ||||||||
3 | Should all the events have same kafka headers | kieran mccarthy Posissbly Common (base) set of headers but mandatory aspect might differ. In practice we might need a separate headers (shema?) for each event | |||||||||
4 | Clarify the format of the version eventSchemaVersion | v1 or 1.0 | kieran mccarthy to check ORAN preference | ||||||||
5 | What to do with additional event headers (from DMI Plugins) | kieran mccarthy if DMI produce Additional headers NCMP will discard those ie. not included in forwarded events | |||||||||
6 | Event(Content) field in DMI Async Request Response Event has inconsistent name (compared with other schemas) |
| CPS Team Create a V2 of the schema and rename eventContent as event. Do it as part of the schema addition. | ||||||||
7 | NCMP Async Request Response Event contains both an Event and ForwardedEvent | ForwardedEvent is not wrapped inside Event but question now is if we need 2 events at all?! Sourabh Sourabh and Raviteja Karumuri can check how it is actually working and then we decide ( create a JIRA ticket ) | |||||||||
8 | Dmi Data AVC Event, use of eventSource field | Priyank Maheshwari wanted to store 'datastore' in this field but kieran mccarthy explained it to use for different purposes | kieran mccarthy Clients can use this field as per their requirements. | ||||||||
9 | Can Kafka Headers be describe with 'schema's owned and managed by NCMP | POC to follow.
Defining header schema. Integration of header with kafka. Naming and versioning convention for the header schemas. | |||||||||
10 | Depending #10 can schema inherit/extend a common schema for common headers | Commonly define them and then define what are mandatory(required) or optional as per the schema extending it. If a field is not used in the extended schema then it should be able to handle it. Extend the POC ( on #9 ) to cover this. | |||||||||
11 | Is anyone using NCMPAsyncRequestReponse EventAsync Request feature? |
| |||||||||
12 | Is 'privateProperties' be Map<String,String> (or) Map<String,Object? | ||||||||||
13 | Do we need additional Properties to use? |
...