Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. 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

XMLWordPrintable

      Sending attached json file with VES event results in the following error (VES Collector log):

       

      StndDefinedSchemaValidator.thresholdInfo.observedValue: More than 1 schema is valid. (code: 1023)
From: StndDefinedSchemaValidator.</opt/app/VESCollector/./etc/externalRepo/3gpp/rep/sa5/MnS/blob/Rel16/OpenAPI/faultMnS.yaml#/components/schemas/NotifyNewAlarm>.<allOf>.thresholdInfo.<#/components/schemas/ThresholdInfo>.observedValue.<oneOf>

       

      This scenario requires exactly the same steps to recreate as DCAEGEN2-2893 with the following changed applied to the yaml file:

       

      # provMnS.yaml remove following lines:
417,419d416
<             - $ref: 'nrNrm.yaml#/components/schemas/resources-nrNrm'
<             - $ref: '5gcNrm.yaml#/components/schemas/resources-5gcNrm'
<             - $ref: 'sliceNrm.yaml#/components/schemas/resources-sliceNrm'

       

      In fact schema 'ThresholdInfo' is defined in both files:

      • faultMnS.yaml
      • genericNrm.yaml

      it's completely different object and as long as the same schema name is used in two different files, it's valid reference. In this case however validator can't determine proper one regardless the fact, that ref in the faultMnS.yaml points to the same file: 

      $ref: '#/components/schemas/ThresholdInfo'

        1. fm_stnd_rel16.json
          2 kB

            deen1985 deen1985
            mwilk mwilk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: