Releases: telefonicaid/fiware-orion
Releases · telefonicaid/fiware-orion
0.18.0
- Add: Service-Path in ngsi10 notifications (Issue #674)
- Add: Forbidden characters in the URL path are now detected (Issue #672)
- Add: X-Auth-Token forwarded in ngsi10 notifications (Issue #673)
- Add: Service-Path is taken into account in ngsi10 subscriptions (Issue #675)
- Fix: Bug: POST /v1/conextEntities didn't save the entity type (from payload) (Issue #684)
- Fix: Service-Path is taken into account in 'GET /v1/contextTypes' and 'GET /v1/contextTypes/{entityType}' operations (Issue #676)
0.17.0
- Add: New convop: "POST /v1/contextEntities" (Issue #613).
- Note also that AppendContextElementRequest has been added an EntityId field.
- Add: Convenience operations that respond with AppendContextElementResponse now get the
- EntityId info included in the response.
- Add: New name for URI param 'attributesFormat': 'attributeFormat' (better English).
- The old name will be supported as well. (Issue #633)
- Add: Fiware-ServicePath '#' syntax for including path children in the query (without '#' only the service path itself is included). (Issue #646)
- Add: "/" is used as implicit service path for entities. (Issue #646)
- Add: Queries without Fiware-ServicePath are resolved on "/#" implicitly (i.e. all the paths). (Issue #646)
- Fix: Attribute type is no longer used as attribute "identification key" (from now on, only name is used for that purpose) (Issue #640)
- Fix: Changed max-length of tenant names from 20 characters to 50.
- Also the database name (CLI-option '-db') has been given a maximum length of 10 bytes. (Issue #616)
- Fix: No longer responding with 'Service not found: $URL'. (Issue #619)
- Fix: Requests with payload containing forbidden characters are now rejected. (Issue #619)
- Fix: Fixed a bug that made the broker crash on problems with EntityId during XML-parse (in very rare situations).
- Fix: 'WSG84' identifier changed to 'WGS84' (it was a typo), although the old one is still supported to ensure backward compatibility. (Issue #627)
- Fix: Fixed a leak for each forwarding of messages to Context Providers.
- Fix: Changed max-length of service path elements from 10 characteres to 50. (Issue #649)
- Fix: Service path is no longer ignored at entity creation time for entities without type. (Issue #642)
- Fix: The broker crashed on receiving compounds for some convops, e.g. /v1/contextEntities/{entityId} (Issue #647)
- Fix: Using 443 as default port for "https" notifications. (Issue #639)
- Fix: Fixed RPM package so PID file is stored in /var/run/contextBroker instead of /var/log/contextBroker. (Issue #612)
- Fix: Payload no longer accepts 'operator' as part of a Scope. (Issue #618)
- Fix: Made compound attribute values for for convenience operations (Issue #660)
0.16.0
- Add: Adding alternative (preferred) URLs: '/ngsi10' => '/v1' AND '/ngsi9' => '/v1/registry' (Issue #559)
- Add: New convenience operation '/v1/contextEntities' - to get a list of ALL existing entities (Issue #563)
- Add: New scopeType FIWARE::Filter::Existence (only with value "entity::type" in this version)
- Add: New URI parameter '!exist=entity::type' to filter entities whose type is empty (Issue #570)
- Add: New conv op URI parameter 'entity::type=TYPE' to filter by type (Issue #570)
- Add: New convenience operations PUT/POST/GET/DELETE /v1/contextEntities/type//id/ (Issue #581)
- Add: New convenience operations PUT/POST/GET/DELETE /v1/contextEntities/type//id//attributes/ATTRIBUTE_NAME (Issue #581)
- Add: New convenience operations PUT/POST/GET/DELETE /v1/contextEntities/type//id//attributes/ATTRIBUTE_NAME/META_ID_VALUE (Issue #581)
- Add: New convenience operations POST/GET /v1/registry/contextEntities/type//id/ (Issue #581)
- Add: New convenience operations POST/GET /v1/registry/contextEntities/type//id//attributes/ATTRIBUTE_NAME (Issue #581)
- Fix: Upgrading from a previous RPM package caused the orion user to disappear.
- Fix: Change service path HTTP header name: 'ServicePath' -> 'Fiware-ServicePath' (Issue #541)
- Fix: Avoid unneeded additional query on csubs/casubs collections to get details of ONCHANGE triggered subscription when processing updateContext (Issue #371)
- Fix: Some convenience operations responsed always with empty type (Issue #585)
- Fix: 'FIWARE_Location' scope type changed to 'FIWARE::Location' (although the old one is still supported)
- Fix: More detailed error responses for some convenience operations:
- POST/DELETE /v1/contextEntities/EID/attributes/ATTR_NAME
- POST/DELETE /v1/contextEntities/type/TYPE/id/ID/attributes/ATTR_NAME
- Also the POST variant of these two URLs always returned 200 OK. Not anymore.
0.15.0
- Add: context providers basic functionality (Issue #499)
- Add: alternative rendering of ContextAttribute for JSON (Issue #490)
- Add: new API operation to retreive all existing context entity types (Issue #519)
- Add: new API operation to retreive all attributes (union set) of a given context entity type (Issue #519)
- Add: support for associations in JSON (Issue #334).
- Add: support for MongoDB replica sets (using the new -rplSet CLI parameter) (Issue #493)
- Fix: Associations now return error messages when appropiate (Issue #334).
- Fix: each send is now considered a separate transaction (Issue #478)
- Fix: lseek after each write in log file in order to work with logrotate truncate (Issue #411)
- Fix: made the broker not support URL-based multiservice (tenants) anymore (Issue #522)
- Fix: removed all the code related to URL-tenants (Issue #522)
0.14.1
- Fix: errors in JSON rendering for '/statistics' and '/version' fixed (Issue #428).
- Fix: using same location attribute in UPDATE fails (issue http://stackoverflow.com/questions/24431177/ge-orion-context-broker-when-we-make-an-update-of-the-entity-does-not-allow-us)
- Fix: Context Broker no crashed anymore due to different tenant names but equal in insensitve case (workaround in Issue #431).
- Logging modifications (Issue #428):
- The name of the log file has been changed from contextBrokerLog to contextBroker.log
- Changed the log line format to use a key-value approach
- Added LM_I, for transactions. Each time a new transaction is initiated, an LM_I is issued. Upon terminating each transaction, another LM_I is issued to reflect this.
- All log lines contain the id of the current transaction, or N/A if no transaction is in progress
- Changed the time reference to localtime (previously GMT was used)
- Stopped using LM_RE, LM_V* and _LM_RVE and removed tho CLI options -v, -vv, -vvv, -vvvv, -vvvvv
- Added an LM_I for when thr broker starts and another when it exits (in a controlled manner).
- The broker now uses libcurl for outgoing HTTP communications.
- Fix: double-quotes in output payload have been escaped (Issue #456)
- Fix: Added tests to make sure that latitude and longitude are within range
(-90 <= latitude <=90) and (-180 <= longitude <= 180) and properly stored in database (Issue #461) - Fix: RPM binary complied in release mode (previous versions used debug)
- Add: file to disable prelinking automatically along with RPM
0.14.0
Changelog since previous version 0.13.0 (FIWARE 3.4.2):
- Add: Pagination, using URI parameters 'offset' and 'limit' (and 'details' for extra details) (issue #395)
- Add: ServicePath support for specifying to which service path entities belong in NGSI10 queryContext and updateContext operations (issue #392)
- Fix: entitiesQuery() method (used in queryContext and NGSI10 subscriptions) has been re-written, making it more clear and optimal (PR #405)
0.13.0
Changelog since previous version 0.12.0 (FIWARE 3.4.1):
- Add: Rush can now be used as relayer for the broker, using the option '-rush' (issue #251)
- Add: Custom metadata support (issue #252)
- Add: Multi-service/tenant support, using the option -multiservice (issue #322)
- Add: Generic URI parameters supported (issue #372)
- Add: Notification mime-type selected in URI parameter 'notifyFormat' (supported values: "XML" and "JSON") (issue #372)
- Fix: Raising error on updateContext with location metadata doesn't involve actual change of location attribute (issue #351)
- Fix: The functionality to change the Log configuration via REST had stopped working. Fixed.
- FIX: The Log configuration via REST used "/log/traceLevel", whereas the documentation states "/log/trace".
Updated the broker to support both "/log/trace" and "/log/traceLevel" - Fix: Changed the XML tags AttributeAssociationList and AttributeAssociation to start with lowercase 'a'. (issue #378)
- Fix: Concatenation of strings now done by the compiler (in numerous places). (issue #384)
- Fix: Passing all complex parameters by reference or pointer (issues #263 and #354)