[Backlogmanager] [FIWARE-JIRA] (HELP-8195) FIWARE.Question.Tech.FIWARE - Orion and STH duplicated notifications.

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-8195:
---------------------------------
     HD-Chapter: Data
    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.


  was:

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-Enabler: Cosmos

> FIWARE.Question.Tech.FIWARE - Orion and STH duplicated notifications.
> ---------------------------------------------------------------------
>
>                 Key: HELP-8195
>                 URL: https://jira.fiware.org/browse/HELP-8195
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>              Labels: duplicates, fiware, fiware-orion, fiware-sth-comet, notifications
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)