The current documentation states that subscriptions can be created via the NGSI-LD API interface of the ThinBroker with a POST ngsi-ld/v1/subscriptions/, but the actual function is not implemented at all: missing on master branch and development branch
Please either remove the subscription part from the documentation or provide an implementation.
It seems that ngsi10/subscribeContext with a Destination=NGSI-LD-header can be used as a workaround. But since the NGSI10 notifyConditions.condValueList is not supported by the current FogFlow implementation (the corresponding data structure exists internally, but it seems that it never gets evaluated), the NGSI-LD behavior of watchedAttributes can't be replicated with the given NGSI10 subscription support.
Additional general question: What is the roadmap of FogFlow regarding NGSI-LD support? I've seen that version 3.2.6 has provided support for quite a lot of NGSI-LD stuff (e.g. #392), but nearly everything was dropped with 3.2.8 (1 year apart). Using a bugfix version for such a breaking change is interesting. How should I understand this procedure? Is native NGSI-LD support not any longer an active goal of the FogFlow development?
The current documentation states that subscriptions can be created via the NGSI-LD API interface of the ThinBroker with a POST
ngsi-ld/v1/subscriptions/
, but the actual function is not implemented at all: missing on master branch and development branchPlease either remove the subscription part from the documentation or provide an implementation.
It seems that
ngsi10/subscribeContext
with aDestination=NGSI-LD
-header can be used as a workaround. But since the NGSI10notifyConditions.condValueList
is not supported by the current FogFlow implementation (the corresponding data structure exists internally, but it seems that it never gets evaluated), the NGSI-LD behavior ofwatchedAttributes
can't be replicated with the given NGSI10 subscription support.Additional general question: What is the roadmap of FogFlow regarding NGSI-LD support? I've seen that version 3.2.6 has provided support for quite a lot of NGSI-LD stuff (e.g. #392), but nearly everything was dropped with 3.2.8 (1 year apart). Using a bugfix version for such a breaking change is interesting. How should I understand this procedure? Is native NGSI-LD support not any longer an active goal of the FogFlow development?