Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4191

FIWARE.Request.Tech.Data.CEP.FIWARE.Bug.Data.CEP.Derivation.MultipleDerivationOfSameEvent

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Chapter:
      Data
    • HD-Enabler:
      CEP

      Description

      Janos Apro sent a message using the contact form at
      http://catalogue.fiware.org/.

      1. There is a bug with EPA derived event saving, sometimes we get different
      settings after reloading the page - I noticed that while creating multiple
      derived events inside one EPA.
      2. I have the following definition for EPA:

      {
      "name": "Treatment",
      "createdDate": "Thu Sep 10 2015",
      "epaType": "Basic",
      "context": "TContext",
      "inputEvents": [

      { "name": "OsmatranjeContextUpdate", "alias": "osmatranje", "consumptionPolicy": "Consume", "instanceSelectionPolicy": "First" }

      ],
      "computedVariables": [],
      "evaluationPolicy": "Immediate",
      "cardinalityPolicy": "Single",
      "internalSegmentation": [],
      "derivedEvents": [
      {
      "name": "TreatmentAlert",
      "condition": "osmatranje.stetocina_id = 22 or
      osmatranje.stetocina_id = 29 or osmatranje.stetocina_id = 30 or
      osmatranje.stetocina_id = 36",
      "reportParticipants": false,
      "expressions":

      { "Duration": "0", "mesto_id": "osmatranje.mesto_id", "stetocina_id": "osmatranje.stetocina_id", "level": "if osmatranje.vrednost > 100 then 2 else 0 endif", "entityId": "osmatranje.mesto_id ++ \"-\" ++ osmatranje.stetocina_id", "entityType": "\"TreatmentAlert\"" }

      },
      {
      "name": "TreatmentAlert",
      "condition": "osmatranje.stetocina_id = 13",
      "reportParticipants": false,
      "expressions":

      { "Duration": "0", "mesto_id": "osmatranje.mesto_id", "stetocina_id": "osmatranje.stetocina_id", "level": "if (osmatranje.vrednost >=5 and osmatranje.vrednost <=8) then 1 elseif osmatranje.vrednost > 8 then 2 else 0 endif", "entityId": "osmatranje.mesto_id ++ \"-\" ++ osmatranje.stetocina_id", "entityType": "\"TreatmentAlert\"" }

      }
      ],
      "derivedActions": []
      }
      ],
      The rule for "level" calculation depends on "stetocina_id".
      If I send the request:

      {"Name" : "OsmatranjeContextUpdate", "stetocina_id" : "36", "mesto_id" : "20034", "vrednost" : "6"}

      I expect to use the 1st rule, and "level" should be 0, but it uses the 2nd
      rule and I get 1.

      We are using the CEP VM from from FIWARE cloud, we can provide its public IP
      address if necessary. The CEP is connected with Orion which has also a public
      IP, it is possible to query the alert in Orion.

      Best regards,
      Janos

      _______________________________________________
      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help-new

      [Created via e-mail received from: aprojanos@gmail.com]

      1. TemperatureAlert.json
        50 kB
        Fabiana Fournier
      2. TemperatureAlert.json
        50 kB
        Fabiana Fournier

        Issue Links

          Activity

          Hide
          TALI Fabiana Fournier added a comment -

          Dear Janos,

          While I created the bug report, I examined your e-mail with the previous EPA definition and I noticed you added the same event twice as derived event (with two different conditions, and with different value assignments in each case). Currently the CEP doesn't support this option. So your work around is the right way to implement what you wanted.

          I will open a bug report, since we should alert the user that this is not supported as part of the verification, or we should add support for it.

          Thanks,
          Tali

          Show
          TALI Fabiana Fournier added a comment - Dear Janos, While I created the bug report, I examined your e-mail with the previous EPA definition and I noticed you added the same event twice as derived event (with two different conditions, and with different value assignments in each case). Currently the CEP doesn't support this option. So your work around is the right way to implement what you wanted. I will open a bug report, since we should alert the user that this is not supported as part of the verification, or we should add support for it. Thanks, Tali
          Hide
          TALI Fabiana Fournier added a comment -

          This is the definition file with the work around. The initial file included the derivation of the same event twice:
          "I have already divided the EPA, I'm sending the current json. The only difference is that I wanted one EPA, 'Treatment' instead of current 'Treatment8' and 'Treatment100'."

          Show
          TALI Fabiana Fournier added a comment - This is the definition file with the work around. The initial file included the derivation of the same event twice: "I have already divided the EPA, I'm sending the current json. The only difference is that I wanted one EPA, 'Treatment' instead of current 'Treatment8' and 'Treatment100'."
          Hide
          TALI Fabiana Fournier added a comment -

          When the user tries to derive the same event in the same EPA twice he gets no error message, but the derivation is not handled correctly.

          Show
          TALI Fabiana Fournier added a comment - When the user tries to derive the same event in the same EPA twice he gets no error message, but the derivation is not handled correctly.
          Hide
          TALI Fabiana Fournier added a comment -

          A bug https://jira.fiware.org/browse/DATA-962 was opened.
          This item should be deleted

          Show
          TALI Fabiana Fournier added a comment - A bug https://jira.fiware.org/browse/DATA-962 was opened. This item should be deleted

            People

            • Assignee:
              TALI Fabiana Fournier
              Reporter:
              TALI Fabiana Fournier
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: