1.5.0
Important note: in the case you use attributes with id metadata, a migration procedure on existing data has to be applied (or DB has to be dropped), see details here.
Full documentation at: http://fiware-orion.readthedocs.io/en/1.5.0/
NGSIv2 API reference (release candidate 2016.10): http://telefonicaid.github.io/fiware-orion/api/v2/stable
Changelog (since 1.4.0):
- Add: Added URI parameter metadata=metadata-name-list for NGSIv2 retrieve requests (#2544)
- Add: Added 'metadata' as part of the payload for POST /v2/op/query (#2544)
- Add: implement 'attrs' (and 'attributes' for POST /v2/op/query) in the same way than 'metadata', including special meaning of '*' (#2455)
- Add: metadata timestamps (dateCreated + dateModified) for attributes (as for entities), including filtering capabilities (#876)
- Add: new value for URI param 'options' (options=noAttrDetail) for NGSIv2 queries to exclude attribute detail, making the query faster (#2073) (*)
- Fix: wrong type in previousValue metadata for notifications triggered by PUT /v2/entities/{id}/attrs/{name}/value (#2553) (*)
- Fix: giving a semaphore in case of mongo exception, which was causing the broker to be unable to serve requests involving the database, and possibly even to crash due to lack of resources (#2571) (*)
- Fix: avoid unused attribute type detail in NGSIv1 queries (which was making the queries slower) (#2073) (*)
- Fix: more accurate actionType in notifications (#2549) (*)
- Fix: over-logging of Runtime Error traces not representing actual error (#2597)
- Fix: support attributes with double underscore as part of the name (#2453)
- Fix: GIT_REV_ORION Docker for master branch needs be master
- Deprecated: dateCreated and dateModified as valid 'options' in NGSIv2 (use 'attrs' instead) (#2455 and #2450)
- Fix: threadpool mode was not actually used, even if -notificationMode is set so; this fix solves the problem for not-custom notifications (partial fix for #2622)
(*) Included also in version 1.4.1.