Releases: FIWARE/context.Orion-LD
Releases · FIWARE/context.Orion-LD
1.0.1
Changes
- introduces an automated release process
- pushes a redhat certification compliant image
1.0.1-PRE-468
Changes
- introduces an automated release process
- pushes a redhat certification compliant image
1.0.0-PRE-460
Changes
- introduces an automated release process
- pushes a redhat certification compliant image
Orion-LD Version 1.0.0
This is the first official release of Orion-LD NGSI-LD Context Broker.
Detailed information on the release found in the 1.0.0 release doc.
Changelog from latest beta release (0.9.0):
- Issue #885 Batch Ops responds with a corrupted payload body if Accept: application/ld+json - fix respond with application/json
- Issue #280 Added a debugging service '/ngsi-ld/ex/v1/ping'
- Issue #280 Performace: saving all DB collection paths ONCE in a tenant-struct instead of creating them before each and every use
- Issue #892 Broker able to receive and act upon NGSI-LD notifications - very first implementation - needs further testing
- Issue #280 Changed the distro for docker images from Debian Stretch to Ubuntu 20.04 - for security and performance reasons
- Issue #897 Fixed a bug in the forwarding mechanism
- Issue #280 Added an URL param 'subscriptionId' to notifications - for ACL in notifications
- Issue #907 CLI param '-noNotifyFalseUpdate' for "no notification when no actual modification has been done"
- Issue #280 Added mongo server version to NGSI-LD version output + better order in the output
- Issue #890 Added check for presence of notification::endpoint when creating subscriptions
- Issue #899 Authorization HTTP header supported for forwarding
- Issue #914 Bug fix for double @context member for GET /attributes?details=true and GET /attributes/{attrName}
- Issue #280 HTTP header NGSILD-Tenant (not FIWARE-Service) in notifications on NGSI-LD subscriptions
- Issue #922 Dynamic allocation of GeoProperties array
- Issue #917 No notification when a compound value is updated without modification
- Issue #926 GET local location of a cached context using URI params location and url - to be able to refresh it in the context cache
- Issue #926 DELETE /contexts/ now also accepts complete URL as "contextId"
- Issue #926 DELETE /contexts/ able to reload contexts (URI param ?reload=true)
- Issue #938 Query on Date-like strings or Datetime
- Issue #925 Bigger char buffer for -troeHost CLI param
- Issue #937 Fixed a Compilation Error in Ubuntu 20.04, RELEASE compilation
- Issue #280 Changed values of HTTP header 'Ngsiv2-Attrsformat' from e.g. 'x-ngsiv2-normalized' to just 'normalized'
- Issue #280 Fixed a problem with the tenant cache for when more than one broker runs against the same DB
- Issue #280 Issue telefonicaid#4012 of Orion repo - HTTPS Key/Certificate max size
Beta 3
This is the Beta 3 release of Orion-LD, an NGSI-LD context broker.
New features with respect to Beta 2 are:
- PATCH requests now support the MIME type
application/marge-patch+json
- datasetId for:
- PATCH /entities/{EID}/attrs/{attrName}
- DELETE /entities/{EID}/attrs/{attrName}
- GET /attributes
- GET /attributes?details=true
- GET /attributes/{attrName}
- GET /types/{typeName}
- POST /temporal/entities
- Services for the @context store/cache that the broker maintains:
- GET /ngsi-ld/v1/jsonldContexts - to get a list of the contexts in the store/cache (
?details=true
also supported) - GET /ngsi-ld/v1/jsonldContexts/{contextId} - to serve an @context
- POST /ngsi-ld/v1/jsonldContexts - to ask the broker to host an @context
- DELETE /ngsi-ld/v1/jsonldContexts/{contextId} - to delete an @context from the context store
- And most importantly, the broker now persists the contexts in DB, so they survive a restart
- GET /ngsi-ld/v1/jsonldContexts - to get a list of the contexts in the store/cache (
Get it on dockerhub
Complete List of fixes (since Beta 2):
- Issue #280 Fixed the response (HTTP Status and payload data) for Batch Create according to update in NGSi-LD API spec
- Issue #280 PATCH ops now support the MIME type 'application/marge-patch+json'
- Issue #280 Removed check for forbidden characters of entity type when inside the payload body
- Issue #280 Better URI validity test
- Issue #280 NGSI-LD entity update requests now provoke notifications regardless on whether any actual change has been done on the entity
- Issue #280 Implemented datasetId for PATCH /entities/{EID}/attrs/{attrName}
- Issue #280 Implemented datasetId for DELETE /entities/{EID}/attrs/{attrName} (supporting URI params 'datasetId' and 'deleteAll')
- Issue #280 Implemented GET /attributes, but only without details=true
- Issue #280 Slightly increased response from Batch Upsert
- Issue #280 Implemented system attributes (createdAt, modifiedAt) for sub-attributes
- Issue #280 Implemented POST /temporal/entities - to add entities to TRoE without actually creating any entity (for the current state)
- Issue #803 Correct HTTP Status Codes for Batch Upsert (201/204/207) according to NGSI-LD v1.3
- Issue #806 Implemented GET /attributes?details=true
- Issue #280 Implemented GET /attributes/{attrName}
- Issue #280 Implemented GET /types/{typeName}
- Issue #807 Important change in context cache - inline contexts are no longer stored in cache
- Issue #280 Experimental implementation of GET /ngsi-ld/v1/contexts (with and without details) - yet to be defined in the NGSI-LD API
- Issue #280 Experimental implementation of GET /ngsi-ld/v1/contexts/{contextId} - yet to be defined in the NGSI-LD API
- Issue #280 Experimental implementation of POST /ngsi-ld/v1/contexts - yet to be defined in the NGSI-LD API
- Issue #280 Experimental implementation of DELETE /ngsi-ld/v1/contexts/{contextId} - yet to be defined in the NGSI-LD API
- Issue #280 Persisting contexts from the cache in mongo
- Issue #280 Added support for MultiPoint in TRoE
- Issue #854 The name of the "value" field was missing in sub-attrs of array or object type in notifications, e.g. "": [1,2,3], instead of "value": [1,2,3]
Orion-LD Beta 2
This is the Beta 2 release of Orion-LD, an NGSI-LD context broker.
New features with respect to Beta 1 are:
- geo+json format supported for:
- entity retrieval
- entity query
- notifications
- Temporal Representation of Entities (in a experimental state)
- Improved Performance
- Bug Fixes
Get it on dockerhub
Complete List of fixes (since Beta 1):
- Issue #280 Implemented a native function for conversion from BSON to a KjNode tree - to gain performance
- Issue #280 Implemented GET /types with options=details
- Issue #280 Much faster response rendering function, giving a performance bump
- Issue #280 GeoJSON formatted response for GET /entities and GET /entities/{EID}, if Accept header set to "application/geo+json"
- Issue #280 GeoJSON formatted notifications, if notification:endpoint:accept is set to "application/geo+json"
- Issue #280 Some requests don't use the @context - e.g. DELETE /entities/{entityId} - those requests now ignore the context
- Issue #280 username, password, and QoS for MQTT notifications - not very tested
- Issue #280 Custom headers for MQTT notifications (using receiverInfo)
- Issue #280 Included
notification::httpInfo::receiverInfo
in subscription retrieval - Issue #280 Fixed a bug about geo+json subscriptions returning the wrong Mime Type (in the notification::endpoint::accept field)
- Issue #732 Fixed the response payload body for GET /types when no types found
- Issue #280 Important concurrency fix - avoiding to download the same context more than once
- Issue #737 Removed the check for forbidden characters in variable names in the 'q' URL parameter
- Issue #280 Fixed the response code and payload body of BATCH Delete
- Issue #280 GET /entities?coordinates=[] didn't allow for the altitude to be present
- Issue #280 Bugfix - location was not included in the response for GET /entities?attrs=X,location
Bugfix 1 for Alpha-6
Fixed a bug regarding geo attribute 'location' in subscriptions
Alpha-6
- Issue #280 Made GET /entities?id=EID call the service routine for /entities/{EID}, if just one single entity id
- Issue #280 Unified all timestamps, with one single call to clock_gettime()
- Issue #550 Added a new notification format for NGSI-LD subscriptions, to notify in NGSIv2 format
- Issue #553 Forwarding X-Auth-Token
- Issue #565 Ability to start broker with traces only to stdout
- Issue #280 Batch Upsert with options=update didn't do what it should - it replaces instead of updates the entities
- Issue #573 URI Check less restrictive than before
- Issue #280 Modify GET /ngsi-ld/v1/types according to the new NGSI-LD spec (1.3.1)
- Issue #280 Fixed Batch Update without options=noOverwrite (didn't replace attributes - now it does)
- Issue #280 Implemented Batch Update with options=noOverwrite
- Issue #280 Default mongo request mutex policy changed from 'all' to 'none'
- Issue #586 Stopped using gtime(), that is not reentrant - gtime_r() is used instead
- Issue #XXX External contributor "@manaty226" fixed an important bug about subscriptions after broker restart - Thanks!
- Issue #605 ORIONLD_MONGO_HOST env var is not parsed correctly - made the buffer for the CLI '-dbHost' bigger (64 -> 1024)
- Issue #559 External contributor "@manaty226" fixed notification on PATCH Entity, updating attributes - Big Thanks!
- Issue #622 unitCode not correctly rendered in NGSI-LD notifications
- Issue #623 "cross-notifications" NGSI-LD to NGSI-V2 with compacted data (attribute names and entity types)
- Issue #652 BATCH Delete with more than one item for the same entity id
- Issue #655 BATCH Create with more than one item for the same entity id
- Issue #658 BATCH Upsert+Replace with more than one item for the same entity id
- Issue #660 BATCH Upsert+Update with more than one item for the same entity id
- Issue #280 BATCH Update with more than one item for the same entity id
- Issue #599 Started with Temporal Representation of Entities (ongoing and highly experimental)
- Issue #280 Made FORWARDING optional - off by default (use CLI -forwarding to turn it on) - for performance reasons
Alpha-5
- Issue #280 Better error handling for geo location
- Issue #280 Version Info printed to stdout (and log-file) at startup
- Issue #280 Fixed the "1001 bug" - a delayed free problem solved by making kjClone() not use always malloc, with an option to use KAlloc
- Issue #280 Avoiding duplicates of entities in Batch Upsert
- Issue #280 All env vars are now prefixed ORIONLD_
- Issue #280 Crash when patching observedAt as sub-attribute
- Issue #280 Subscriptions when deleted were not removed from the subscription cache - now they are
- Issue #482 Fixed "Part C" - Notifications of big size attributes are cut off at 2049 Byte total message length
- Issue #482 Fixed "Part B" - Size constraints on entity size for GET /entities/{entity-id}
- Issue #480 Erroneous contexts are saved in the context cache
- Issue #482 Error following the 482 fix, too small buffer of delayed free references - upped to 1001 slots
- Issue #280 Crash in startup if a huge amount of GeoProperties in the database
- Issue #280 @id and @type can now be used instead of id and type
- Issue #280 milliseconds for ALL timestamps, including throttling, notifiedAt, observation and management intervals, etc, etc
- Issue #280 Implemented createdAt and modifiedAt + options=sysAttrs for subscriptions (with milliseconds, of course)
- Issue #280 createdAt and modifiedAt for registrations were returned as integers - now as ISO8601 strings (with milliseconds)
- Issue #280 Returning 501 Not Implemented if timeInterval is used for subscriptions
- Issue #430 Accepting "?options=count" as well as "?count=true" in NGSI-LD queries, for backwards compatibility
- Issue #507 Core context instead of the one in the Link header used in Batch Update
- Issue #280 User defined HTTP headers for notifications (part of NGSI-LD 1.3.1)
- Issue #520 Fixed bug in POST /entities with datasetId
- Issue #521 Implemented datasetId for POST entities/*/attrs
- Issue #525 Error handling in responses to forwarded GET /entities/{entityId} (the broker used to crash)
- Issue #529 Subscriptions stop working after restarting the broker
- Issue #532 Return error if unknown URI parameter is used
- Issue #527 Bug in update of relationships with datasetId
- Issue #280 Fixed Release Mode compilation errors in Ubuntu 20.04
- Issue #280 Removed the feature of expanding attribute values as it doesn't fit with JSON-LD
Docker: docker pull fiware/orion-ld:alpha-0.5.0
Alpha-4
Find the docker image for fiware/orion-ld:alpha-0.4.0
on dockerhub
- Issue #280 MQTT Notifications - not 100% - ETSI NGSI-LD spec is still being updated on MQTT notifications, but what's there is working
- Issue #409 Removed an incorrect warning about options=keyValues not supported
- Issue #280 'location' is not to be expanded - fixed for PATCH ops that was expanding 'location'
- Issue #280 Implemented POST /ngsi-ld/v1/entityOperations/create (BATCH Create)
- Issue #280 Added the option to use username:password for MQTT subscriptions (only 'QoS' and 'version' missing now for MQTT notifications)
- Issue #419 Implemented GET /ngsi-ld/v1/types - also not yet in the spec, so this may change slightly in the near future
- Issue #280 Fixed a bug that impeded the creation of registrations with only entity-type in the entities array
- Issue #280 Entities can now have more than one GeoProperty
- Issue #280 Turned off initial notifications (when creating NGSI-LD subscriptions)
- Issue #280 New version for the 'count' URI parameter - in NGSI-LD 'options' isn't used for 'count'
- Issue #280 Implemented POST /ngsi-ld/v1/entityOperations/update (BATCH Update)
- Issue #280 Fixed bug in context cache that didn't save some contexts in the cache and made them being downloaded each and every time
- Issue #280 New DB layer for GET /entities/{EID} - mongoBackend no longer used
- Issue #280 datasetId partly supported for creation of entities
- Issue #280 datasetId partly supported for retrieval of entities
- Issue #451 When retrieving an entity, if attrs URI param 'attrs' is given and the entity doesn't have any of those attributes, a 404 is returned
- Issue #280 Two new NGSI-LD error codes: NoMultiTenantSupport and NonExistingTenant
- Issue #280 Error when non-existing tenant is used (except for creation)
- Issue #457 creDate can now be either a float, an int or a long in some functions (e.g. batch upsert)
- Issue #280 Implemented the POST Query request - POST /ngsi-ld/v1/entityOperations/query