Skip to content

3.11.0

Compare
Choose a tag to compare
@fgalan fgalan released this 29 Jan 08:18
· 393 commits to master since this release

Full documentation at: http://fiware-orion.readthedocs.io/en/3.11.0/

NGSIv2 API reference: https://github.com/telefonicaid/fiware-orion/blob/3.11.0/doc/manuals/orion-api.md


IMPORTANTE NOTE: location metadata to specify entity location (deprecated in Orion 1.1.0 in May 2016) has been removed. In order to know if you have some entity using that feature you can use the entities consistency script. Do a check before upgrading using Rule94 (detect usage of not redundant legacy location), this way:

entities_consistency.py --mongoUri mongodb://<your MongoDB connection string> --logLevel INFO --rules-exp Rule94

if you find some entity violating that rule, then apply the Rule94 suggested actions to fix it:

  • Change attribute type to geo:json
  • Set the attribute value to the same GeoJSON in location.coords field
  • Remove the location metadata from the attribute

Changes (since 3.10.0):

  • Add: notification.mqtt.retain and notification.mqttCustom.retain flag for MQTT retain in notifications (#4388)
  • Add: CLI parameter -dbUri / env var ORION_MONGO_URI (#3794)
  • Add: servicePath field to builtin attributes (#2877)
  • Add: notification payload in INFO log traces (#4449)
  • Add: log deprecation traces for usage of legacyForwarding mode in registrations
  • Add: log deprecation traces for usage of attrsFormat legacy in subscriptions
  • Add: deprecatedFeatures counters block in GET /v2/statistics
  • Fix: correctly detect JSON attribute and metadata value changes in subscription triggering logic (#4211, #4434, #643)
  • Fix: do not show dateExpires built-in attribute in GET /v2/types and GET /v2/types/{type} operations (#4451)
  • Fix: builtin attributes alterationType, dateCreated and dateModified included in notifications even when onlyChangedAttrs is true
  • Fix: update forwarding was not working when entity type is not included in the request (#4460)
  • Fix: DateTime and geo:json types were not supported in custom notifications using ngsi patching (#4435)
  • Fix: in custom notification NGSI payload patching macro subscription covering completely the string where is used, always cast to string for id/type (#4462)
  • Fix: on delete attributes operation, the lack of attribute in entity doesn't preclude the deletion of attributes which do exist (this way behaving same way as update attributes operation)
  • Fix: POST /v2/entities/E/attrs?options=append was wrongly creating entities
  • Fix: provide more informative error description in some error responses in update/delete operations
  • Fix: proper use of "PartialUpdate" (instead of "Unprocessed") in responses in the case of partial updates/deletions (#3499)
  • Fix: response 404 Not Found "NotFound" errors instead of 422 Unprocessable Content "Unprocessed" in the case of missing attribute in existing entity in attribute update operations
  • Fix: "Internal Server Error" changed to "InternalServerError" in error responses
  • Fix: improve logs in MongoDB query logic
  • Fix: logDeprecate not working correctly (geo:json wrongly considered as deprecated) (*)
  • Fix: false positive in log deprecation logic when entity name (or other literal) includes the token "v1" (#4454)
  • Fix: improve error traces (#4387)
  • Hardening: upgrade libmongoc dependency from 1.23.1 to 1.24.3
  • Reference MongoDB version changed from 4.4 to 6.0
  • Reference distribution changed from Debian 11 to Debian 12
  • Upgrade Debian version from 11.6 to 12.4 in Dockerfile
  • Remove: deprecated NGSIv1 location metadata to specify entity geo-location

(*) Also included in hotfix version 3.10.1