You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was playing with NGSI-LD subscriptions when I discovered an issue. Following the ETSI CIM standard and the specification document for the NGSI-LD API V1.6.1 (i.e., ETSI GS CIM 009 V1.6.1), which is supported by ORION-LD Context Broker, according to the section 5.2.14 NotificationParams (Table 5.2.14.1-1: NotificationParams data type definition on page 82), there is a notification parameter named sysAttrs that "if true, the system generated attributes createdAt and modifiedAt are included in the response payload body, in the case of a deletion also deletedAt". But I've checked that creating a simple subscription with the sysAttrs notification parameter does not work well because the sysAttrs parameter is not recognize. The same issue happens with the showChanges notification parameter (also described in Table 5.2.14.1-1: NotificationParams data type definition on page 82).
Yeah, both "showChanges" and "sysAttrs" in Subscriptions are new additions to the NGSI-LD API spec (added in v1.6.1).
They aren't supported yet by Orion-LD.
Curiously a few days ago I had another user asking for "showChanges", and I just finished implementing part 1 of that.
Part 1 is the basic case, not including BATCH operations, deletions, nor distributed operations: #1396
I hope to merge this PR today.
About "sysAttrs", sure, if you need that feature I can start implementing that pretty much right now.
Thank you so much for your quick answer! From my point of view, it would be very interesting to be able to indicate whether or not to receive those "createdAt", "modifiedAt", and "deletedAt" fields in the notifications received for a demanded subscription. This "sysAttrs" field seems a great decision from the ETSI CIM specification for the NGSI-LD API :)
Hi everyone,
I was playing with NGSI-LD subscriptions when I discovered an issue. Following the ETSI CIM standard and the specification document for the NGSI-LD API V1.6.1 (i.e.,
ETSI GS CIM 009 V1.6.1
), which is supported by ORION-LD Context Broker, according to the section 5.2.14 NotificationParams (Table 5.2.14.1-1: NotificationParams data type definition on page 82), there is a notification parameter namedsysAttrs
that "if true, the system generated attributes createdAt and modifiedAt are included in the response payload body, in the case of a deletion also deletedAt". But I've checked that creating a simple subscription with thesysAttrs
notification parameter does not work well because thesysAttrs
parameter is not recognize. The same issue happens with theshowChanges
notification parameter (also described in Table 5.2.14.1-1: NotificationParams data type definition on page 82).Let me show an example:
Environment
Making the following HTTP GET request for getting the ORION-LD Context Broker version:
, the regarding response body is the following:
Steps to reproduce
Sensor
NGSI-LD Entity with thesysAttrs
notification parameter:, the regarding response body is the following:
Sensor
NGSI-LD Entity with theshowChanges
notification parameter:, the regarding response body is the following:
Many thanks in advance!
Dani
The text was updated successfully, but these errors were encountered: