fiware-orion | Context Broker and CEF building block

I had a similar use case, found a simple solution:

1. Change matrix range to a list of objects, containing order and range.
2. Concatenate order with the job's name key.
3. Use range key as before.

Hopefully, Github Actions will add an index to the matrix jobs, simplifying the way we distinguish between them.

I'd say that the request headers that are being forwarded are:

• fiware-correlator
• fiware-service
• fiware-servicepath
• x-auth-token

For more detail, I'd recommend to have a look to the httpSendRequest() function implementation in the Orion Context Broker code.

I think I found the answer myself just after publishing the question (use to happen :)

Adding to the .includes file this line:

Are sure the thread is in a cancelation or your thread cancelation_type is asynchronous?

From man of pthread_cancel:

A thread's cancellation type, determined by pthread_setcanceltype(3), may be either asynchronous or deferred (the default for new threads). Asynchronous cancelability means that the thread can be canceled at any time (usually immediately, but the system does not guarantee this). Deferred cancelability means that cancellation will be delayed until the thread next calls a function that is a cancellation point. A list of functions that are or may be cancellation points is provided in pthreads(7).

I don't think canceling threads is the best ways to make sure that a thread will finish. Perhaps you can send the thread a message that it should stop and make sure the thread does receive the message and will handle it.

Not sure if I'm fully understanding you case...

You could do a registration for all citizen like this one:

The NGSIv2 method that allows to update several entities at once is POST /v2/op/update. It uses as parameter an array of entities:

entities, an array of entities, each entity specified using the JSON entity representation format (described in the section "JSON Entity Representation").

and in the cited "JSON Entity Respresentation" section we have:

An entity is represented by a JSON object with the following syntax:

• The entity id is specified by the object's id property, whose value is a string containing the entity id.
• The entity type is specified by the object's type property, whose value is a string containing the entity's type name.
• Entity attributes are specified by additional properties, whose names are the name of the attribute and whose representation is described in the "JSON Attribute Representation" section below. Obviously, id and type are not allowed to be used as attribute names.

Thus, in conclusion, you cannot use a pattern of entities to update.

However, this has an easy workaround: you can create and script (or logical function in a wider program) to do that work, basically:

• To query Orion with a given pattern, getting a set of entity (taking into account pagination, if the number of entities is large).
• To update all these entities with POST /v2/op/update (taking into account doing it in batches, as there is a limit of 1MB in Orion request, if the number of entities to update is large).

You can have a look to this script, which works in this way (although in this case is to delete a set of entities instead of updating an attribute).

Not as far as I know, but it should be easy to do with a shell script and curl. Another option is through the mongoDB collection, but that would be a hack that could lead to inconsistencies ...

In multi node deployment of Orion ContextBroker as described in referred document, there will be one notification to each event from the broker which will receive the request. The HAProxy will route each incoming request to one of multiple ContextBroker, thus one notification will be generated based on subscription made.

So If you Register/subscribe to an specific Event, then, you will be notified/called one time from one ContextBroker which has received the reuqest.