Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
HD-Chapter:Data
-
HD-Enabler:Orion
Description
Created question in FIWARE Q/A platform on 28-01-2017 at 21:01
Please, ANSWER this question AT https://stackoverflow.com/questions/41914246/fiware-orion-and-sth-duplicated-notifications
Question:
FIWARE - Orion and STH duplicated notifications
Description:
I have a scenario where two or more subscriptions were made to some entity (with the same notification url). In this case, I have many of the same subscriptions. When the attributes related to subscriptions conditions are updated, I have as many notifications as subscriptions I made. This way, I have unnecessary messages, resulting in unnecessary processing.
Is there a way to deal with this? Both Orion and STH Comet do not handle with this. Maybe Orion and STH can deny the creation of a subscription that already exists. If this Orion behavior is updated, maybe STH Comet does not need to handle that.
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
2h 56m | 1 | Backlog Manager | 22/May/17 6:07 PM | |||||
|
3h | 1 | Backlog Manager | 22/May/17 9:07 PM |
Fix Version/s | 2021 [ 12600 ] |
Assignee | Backlog Manager [ backlogmanager ] |
HD-Enabler | Orion [ 10875 ] | |
HD-Chapter | Data [ 10838 ] |
Resolution | Done [ 10000 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
2017-05-22 21:08|UPDATED status: transition Finish| # answers= 1, accepted answer= True