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:Cosmos
Description
Created question in FIWARE Q/A platform on 28-01-2017 at 21:01
Please, ANSWER this question AT http://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
| Field | Original Value | New Value |
|---|---|---|
| Component/s | FIWARE-TECH-HELP [ 10278 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
2017-01-29 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
2017-01-29 21:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
2017-01-30 00:05|UPDATED status: transition Finish| # answers= 1, accepted answer= True
| Summary | [fiware-stackoverflow] FIWARE - Orion and STH duplicated notifications | FIWARE.Question.Tech.FIWARE - Orion and STH duplicated notifications. |
| HD-Enabler | Cosmos [ 10872 ] | |
| Description |
Created question in FIWARE Q/A platform on 28-01-2017 at 21:01 {color: red}Please, ANSWER this question AT{color} http://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. |
Created question in FIWARE Q/A platform on 28-01-2017 at 21:01
{color: red}Please, ANSWER this question AT{color} http://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. |
| HD-Chapter | Data [ 10838 ] |
| Assignee | Jose Manuel Cantera [ jmcantera ] |
| Fix Version/s | 2021 [ 12600 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
20h 59m | 1 | Backlog Manager | 29/Jan/17 6:05 PM | |||||
|
3h | 1 | Backlog Manager | 29/Jan/17 9:05 PM | |||||
|
3h | 1 | Backlog Manager | 30/Jan/17 12:05 AM |
2017-01-28 21:05|CREATED monitor | # answers= 0, accepted answer= False