We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

Multiple subscriptions in batch mode

asked 2021-05-28 09:26:23 +0200

pasquy73 gravatar image

Hi all, I created multiple notifications using idPattern (Car[1-5]) to sent notifications for any Cars of the same type to save data using Cygnus. Subscriptions works! I can update any attribute (i.e. /v2/entities/Car1/attrs/speed). But can I use a batch operation (v2/op/update) to update multiple attrs? I tried but only one (first) attribute will be notified (and stored) If yes, what can I do it? I also tried to configure CYGNUSMYSQLBATCH_xxx params but without success. Thank you pasquy

edit retag flag offensive close merge delete


Probably this question should be posted in https://stackoverflow.com (using the "fiware-orion" label) to reach a wider audience

Fermín Galán gravatar imageFermín Galán ( 2021-06-16 13:07:37 +0200 )edit

1 answer

Sort by » oldest newest most voted

answered 2021-06-02 09:28:41 +0200

The subscriptions have a field to "narrow down" the notifications, only including those attributes that the subscription "asks to be included". Perhaps this is why you get only the first attribute in the notifications. If this is not the case, then it may be a bug in Orion. If you feel that it is a bug, the way to go is to report it as an issue on Orion's github - https://github.com/telefonicaid/fiwar..., giving a complete description of the problem, including all details, e.g. the exact payload body and headers that was used when creating the subscriptions, same same for the batch update operation. Also, version of the broker (output from GET /version) and anything else you feel might be useful to reproduce the problem.

edit flag offensive delete link more


Singular notifications (/v2/entities/Car1/attrs/speed and /v2/entities/Car2/attrs/speed) are fine. Of course, I'm using the same headers (for all). But only the first entity (Car1) will be notified if I change the speed attribute for both, using /v2/op/update API.

pasquy73 gravatar imagepasquy73 ( 2021-06-07 13:41:52 +0200 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2021-05-28 09:26:23 +0200

Seen: 639 times

Last updated: Jun 02 '21