Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-6316

FIWARE.Request.Tech.Data.OrionContextBroker.Orion Context Broker subscriptions question

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:
          None

          Description

          Hi,

          as I read, Orion CB will send a notification as soon as a new subscription
          is created, because (quoting) "Orion Context Broker considers the
          transition from "non existing subscription" to "subscribed" as a change."
          Is there a way to avoid first notification with ONCHANGE subscriptions,
          without having to manually check in code (eg: with a firstTime boolean)?
          As i'm developing an android app, i find it rather stupid that as soon as
          an user enables a rule, he gets spammed with an useless (at that time)
          notification.

          Thank you very much,
          Federico Di Pierro

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-incense-coaching@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-incense-coaching mailing list
          Fiware-incense-coaching@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-incense-coaching
          [Created via e-mail received from: Federico Di Pierro <f.dipierro@atooma.com>]

            Issue Links

            relates to

            extRequest - Request from external stakeholder received in the help desk HELC-1334 FIWARE.Request.Coach.INCENSe.Orion Context Broker subscriptions question

            • Major - Major loss of function.
            • Closed

              Activity

              Descending order - Click to sort in ascending order
              Transition Time In Source Status Execution Times Last Executer Last Execution Date
              Open Open In Progress In Progress
              		8h 2m 1 Fermín Galán 05/Apr/16 7:02 PM
              In Progress In Progress Answered Answered
              		2s 1 Fermín Galán 05/Apr/16 7:02 PM
              Answered Answered Closed Closed
              		1s 1 Fermín Galán 05/Apr/16 7:02 PM
              fla Fernando Lopez made changes -
              Fix Version/s 2021 [ 12600 ]
              mev Manuel Escriche made changes -
              Sender Email f.dipierro@atooma.com
              backlogmanager Backlog Manager made changes -
              Summary [Fiware-incense-coaching] Orion Context Broker subscriptions question FIWARE.Request.Tech.Data.OrionContextBroker.Orion Context Broker subscriptions question
              HD-Node Unknown [ 10852 ]
              Hide
              Permalink
              fw.ext.user FW External User added a comment -

              Thanks, voted.
              Making it configurable would be a huge step forward.

              Again, thank you very much.

              Federico Di Pierro

              Show
              fw.ext.user FW External User added a comment - Thanks, voted. Making it configurable would be a huge step forward. Again, thank you very much. Federico Di Pierro
              fermin Fermín Galán made changes -
              Resolution Done [ 10000 ]
              Status Answered [ 10104 ] Closed [ 6 ]
              fermin Fermín Galán made changes -
              Status In Progress [ 3 ] Answered [ 10104 ]
              fermin Fermín Galán made changes -
              Status Open [ 1 ] In Progress [ 3 ]
              Hide
              Permalink
              fermin Fermín Galán added a comment -

              The issue has been emailed:

              • Time sent: 05/Apr/16 6:55 PM
              • To: f.dipierro@atooma.com
              • with subject: *(HELP-6316) [Fiware-incense-coaching] Orion Context Broker subscriptions question *

              Dear Federico,

              Initial notification is synchronous to the subscription operation, thus is a way of getting the "initial state" of the context covered by the subscription before starting getting notifications. You could argue that a a syncronous query operation (e.g. GET /v2/entities, etc.) could be used to get the initial state at the same time of doing the subscription, but race conditions may occur beetween both operations so the initial notification is a more precise mechanism.

              Is this precise "initial state" useless? Well, it depends on the use case. The optimal solution would be to make this feature configurable and we have an open issue about that:

              https://github.com/telefonicaid/fiware-orion/issues/920

              Please add a +1 to that issue if you suppor the idea. Thanks!

              Best regards,

              ------
              Fermín

              Show
              fermin Fermín Galán added a comment - The issue has been emailed: Time sent: 05/Apr/16 6:55 PM To: f.dipierro@atooma.com with subject: *( HELP-6316 ) [Fiware-incense-coaching] Orion Context Broker subscriptions question * Dear Federico, Initial notification is synchronous to the subscription operation, thus is a way of getting the "initial state" of the context covered by the subscription before starting getting notifications. You could argue that a a syncronous query operation (e.g. GET /v2/entities, etc.) could be used to get the initial state at the same time of doing the subscription, but race conditions may occur beetween both operations so the initial notification is a more precise mechanism. Is this precise "initial state" useless? Well, it depends on the use case. The optimal solution would be to make this feature configurable and we have an open issue about that: https://github.com/telefonicaid/fiware-orion/issues/920 Please add a +1 to that issue if you suppor the idea. Thanks! Best regards, ------ Fermín
              backlogmanager Backlog Manager made changes -
              Assignee Fermín Galán [ fermin ]
              backlogmanager Backlog Manager made changes -
              HD-Chapter Unknown [ 10845 ] Data [ 10838 ]
              mev Manuel Escriche made changes -
              HD-Enabler Unknown [ 10910 ] Orion [ 10875 ]
              backlogmanager Backlog Manager made changes -
              HD-Enabler Unknown [ 10910 ]
              HD-Chapter Unknown [ 10845 ]
              HD-Node Unknown [ 10852 ]
              backlogmanager Backlog Manager made changes -
              Field Original Value New Value
              Link This issue relates to HELC-1334 [ HELC-1334 ]
              backlogmanager Backlog Manager created issue -

                People

                • Assignee:
                  fermin Fermín Galán
                  Reporter:
                  fw.ext.user FW External User
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: