Fermín Galán Márquez
Fermín Galán Márquez
**Is your feature request related to a use case?** In some situations we need more flexibility in cache management. In particular: * To check the contents of the cache *...
Running test case ``` ./testHarness.sh cases/3533_null_in_datetime_and_geo/null_in_geo_point.test ``` if we look to Context Broker traces looking for WARN level: ``` $ cat /tmp/contextBroker.log | grep WARN time=2021-05-24T11:53:33.360Z | lvl=WARN | corr=aa4a7a4c-bc86-11eb-a2f4-000c29df7912...
Implement an extension of the `GET /v2/entities` operation extending it with aggregation operations. For instance, to aggregate by attribute `category`, getting how many entities are in each category: ``` GET...
A way of using alias for notification endpoints, so instead of using the full URL en the subscription (with host, port and path) the alias will be used. Some benefits...
For `POST /v2/op/update` (and for the batch operations described at https://github.com/telefonicaid/fiware-orion/issues/2388, in the case that issue gets considered at the end) allow entity patterns. Currently the `entities` vector only allows...
After some internal discussion, we have decided that the processing of Feature and FeatureCollection geo:json attributes (issue #4114) will involve a normalization in GET/notification stage. That is, CB will accept...
Creating entity this way: ``` curl -iX POST 'http://localhost:1026/v2/entities' \ -H 'Content-Type: application/json' \ -d ' { "id": "E", "type": "T", "location": { "type": "geo:json", "value": { "type": "Point", "coordinates":...
**Is your feature request related to a problem / use case? Please describe.** NGSIv2 supportS geo-queries based in the following * `georel` (disjoint, etc.) * `geometry` (point, line, etc.) *...
**Is your feature request related to a problem / use case? Please describe.** Orion is able to log in the case of notification queue is full (in threadpool notification model),...
We have transient entities functionality since Orion 1.15.0. However, in addition of using a fixed date it will be great to add the capability of expire (and delete) the entity...