Releases: telefonicaid/fiware-orion
1.7.0
Full documentation at: http://fiware-orion.readthedocs.io/en/1.7.0/
NGSIv2 API reference (release candidate 2016.10): http://telefonicaid.github.io/fiware-orion/api/v2/stable
Changelog (since 1.6.0):
- Add: HTTPS native notifications (#706), fixing at the same time issue #2844
- Add: new option to accept self-signed certifications used by HTTPS notification endpoints: -insecureNotif (#706)
- Add: metrics REST API (#2750)
- Add: new option to set the timeout for REST request: -reqTimeout (#2762)
- Add: the string "ISO6801" can now be used as an alias for "DateTime" as type for attributes and metadata (#2654)
- Add: new CLI '-disableMetrics' to disable metrics (#2750)
- Add: support for quotes (') in string filters to let attribute/metadata names contain dots (#2805)
- Add: Support for null values in string filters (#2359)
- Add: one more semaphore (the metrics semaphore) to the semWait block in GET /statistics and to the list in GET /admin/sem (#2750)
- Fix: libmicrohttpd now uses poll()/epoll() and not select() so fds greater than 1023 can be used for incoming connections (#2724, #2166)
- Fix: modified the upper limit for CLI '-maxConnections', from 1020 to UNLIMITED
- Fix: proper 500 Internal Server Error response with descriptive text when "sort fail" at DB occur (#2752)
- Fix: giving a descriptive response with payload, without reading the request for too big payloads (#2761)
- Fix: check for forbidden chars in entity type and id in POST /v2/op/query request (#2819)
- Fix: removed check for forbidden chars in URI param typePattern (#2819)
- Fix: checking for forbidden characters inside the components of string filters (#1994)
- Fix: including Service-Path in notifications also when the service path is the default one (/). For notifications due to 'standard subscriptions', notifications due to 'custom subscriptions' already work this way (#2584)
- Fix: NGSIv1 updateContext APPEND on existing geo:point attributes (and probably other geo: attributes) failing to update location (#2770)
- Fix: bug when tenants are over 44 bytes long (#2811)
- Fix: pattern matching in q/mq: pattern is always a string (#2226)
- Fix: Partial sanity check for custom url, only if the url contains no replacements using ${xxx} (#2280, #2279)
- Fix: Stricter validity check of URL before accepting a subscription (#2009)
- Fix: if entity::type is given but as an empty string, in payload of POST /v2/subscriptions or PATCH /v2/subscriptions/{sub}, an error is returned (#1985)
- Fix: more intelligent, quote-aware, operator lookup inside q/mq string filters (#2452)
- Fix: weird 'md: { }' added with some update operations (#2831)
- Fix: attribute names that include ':' now are supported, with the single-quote syntax. E.g. q='devices:location' (#2452)
- Fix: admin requests (such as GET /version) with errors now return '400 Bad Request', not '200 OK'
- Fix: attempt to create an entity with an error in service path (and probably more types of errors) now returns '400 Bad Request', not '200 OK' (#2763)
- Fix: not calling regfree when regcomp fails. Potential fix for a crash (#2769)
- Fix: wrongly overlogging metadata abscense in csub docs as Runtime Error (#2796)
- Fix: if HTTP header Content-Length contains a value above the maximum payload size, an error is returned and the message is not read (#2761)
- Fix: no longer accepting a service path with an empty component (e.g. /comp1//comp3) (#2772)
- Fix: bug in notification queue statistics, "in" value (#2744)
- Fix: Accept header errors in NGSIv2 requests were incorrectly being rendered using "OrionError" element (#2765)
1.6.0
Full documentation at: http://fiware-orion.readthedocs.io/en/1.6.0/
NGSIv2 API reference (release candidate 2016.10): http://telefonicaid.github.io/fiware-orion/api/v2/stable
Changelog (since 1.5.0):
- Add: notification failure/recovery information included in subscriptions (#1960)
- Add: support ISO8601 timezones at DateTime attributes and metadata creation/update time and filters (#2632)
- Add: support for partial representation format at DateTime attributes and metadata creation/update and filters (#2631)
- Add: New CLI option: '-logForHumans', to make the screen log output readable for humans (#2609)
- Fix: threadpool mode not actually used for custom notifications, even if -notificationMode is set so (#2622) (*)
- Fix: -logAppend as default in configuration for RPM package (#2637) (*)
- Fix: Default log output for stdout is now the same format as in the log file. Use new CLI option '-logForHumans' to modify this. (#2609)
- Fix: several bugs related with field validation in POST /v2/op/update operation (#2653, #2658, #2659, #2661, #2664, #2665, #2666, #2673, #2674, #2675, #2676, #2681, #2682, #2685)
- Fix: subscription PATCH not working for notification.attrs and notification.exceptAttrs subfields (#2647)
- Fix: PATCH attr wrongly adding metadata item instead of replacing (#1788)
- Fix: POST /v2/op/update with empty entities vector makes the broker to crash (#2720) (*)
- Fix: allow empty elements in Accept header (useless, but allowed by HTTP RFC) (#2722) (*)
- Fix: NGSIv1 queries are wrongly interpreting entity type as a pattern (#2723) (*)
- Fix: improving performance avoiding unneeded calls to gettid in log library (#2716)
(*) Included also in some 1.4.x versions.
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
Important note: in the case you use attributes with id metadata, and you come from 1.4.1 or 1.4.10 the same migration procedure on existing data defined for 1.5.0 has to be applied (or DB has to be dropped), see details here.
Changes (since 1.4.1):
- 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: 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)
- Fix: threadpool mode not actually used for custom notifications, even if -notificationMode is set so (#2622)
- Fix: -logAppend as default in configuration for RPM package (#2637)
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.
1.2.4
1.4.1
Changelog (since 1.4.0):
- 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)