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": [
],
"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":
},
{
"name": "TreatmentAlert",
"condition": "osmatranje.stetocina_id = 13",
"reportParticipants": false,
"expressions":
}
],
"derivedActions": []
}
],
The rule for "level" calculation depends on "stetocina_id".
If I send the request:
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]
Issue Links
- clones
-
HELP-4074 FIWARE.Request.Tech.Data.CEP.bug in EPA event derivation
- Closed
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