Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Data
-
HD-Enabler:Orion
Description
Created question in FIWARE Q/A platform on 28-12-2015 at 11:12
Please, ANSWER this question AT https://stackoverflow.com/questions/34491828/fiware-orion-context-broker-metadata-updates-trigger-notifications
Question:
FIWARE-Orion Context Broker metadata updates trigger notifications
Description:
I'm using 3 FIWARE GEs: IDAS+Orion+CEP.
As reported in the Orion documentation (https://github.com/telefonicaid/fiware-orion/blob/develop/doc/manuals/user/metadata.md) "changing the metadata of a given attribute or adding a new metadata element is considered a change even if attribute value itself hasn't changed".
Is there a way to send notifications from Orion only if the value of the attribute specified in the subscription changes?
I've tried the solution proposed in the documentation, delete and re-create the attribute, in order to remove the metadata. But, since the messages to Orion are produced by IDAS, the metadata are created with the new communication.
Thanks.
UPDATE:
GEs Version:
- Orion - 0.26.1-next
- IoTAgent (IDAS) - 1.3.1
The metadata added by IDAS are:
"attributes" : [
{
"name" : "temperature",
"type" : "int",
"value" : "37",
"metadatas" : [
]
}
]
Specifically, from mongodb query:
"temperature" : { "value" : "37", "type" : "int", "md" : [
{ "name" : "TimeInstant", "type" : "ISO8601", "value" : "2015-12-29T12:46:04.421859" }], "creDate" : 1450716887, "modDate" : 1451393164 }
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Assignee | Fermín Galán [ fermin ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
HD-Enabler | Orion [ 10875 ] | |
HD-Chapter | Data [ 10838 ] |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
2h 57m | 1 | Backlog Manager | 22/May/17 6:05 PM | |||||
|
3h | 1 | Backlog Manager | 22/May/17 9:05 PM | |||||
|
6d 14h 28m | 1 | José Ignacio Carretero Guarde | 29/May/17 11:34 AM |
2017-05-22 15:09|CREATED monitor | # answers= 1, accepted answer= False