-
Task
-
Resolution: Won't Do
-
Medium
-
Istanbul Release
VES Collector stndDefinedFields schema validation mechanism is following all the references recursively from all the referenced files and URIs, instead of following the relevant individual schemas instead. This causes unnecessary overkill, performance issues and waste of resources.
Follow the recreation instructions provided in the DCAEGEN2-2893 to find out that in order to validate Fault event against top level schema: https://forge.3gpp.org/rep/sa5/MnS/blob/Rel16/OpenAPI/faultMnS.yaml#components/schemas/NotifyNewAlarm
it tries to follow all references, ie:
comDefs.yaml -> provMnS.yaml -> 5gcNrm.yaml -> https://forge.3gpp.org/rep/all/5G_APIs/raw/REL-16/TS29512_Npcf_SMPolicyControl.yaml
which in case of NotifyNewAlarm is irrelevant.
- relates to
-
DCAEGEN2-2893 VES Collector stndDefinedFields schema validation issue
- Closed
-
DCAEGEN2-2894 VES Collector fails to validate event against schema if more that one file in the repository contains schema definition of a given name
- Closed