Orion-ld after 0.8.0 is not supporting the formation of service/subservice in quantumleap logs

[tonyrosset]

Any version of orion-ld after 0.8.0 is not supporting the formation of service/subservice in quantumleap logs, thereby no table-schema formed with "mt" prefix in crate-db. But tables are formed with "et" prefix followed by entity type containing quantumleap persisted data.

Below is my example quantumleap subscription

{ "description": "Notify me of animal locations", "type": "Subscription", "entities": [{"type": "Device"}], "watchedAttributes": ["location", "status", "heartRate"], "notification": { "attributes": ["location", "status", "heartRate"], "format": "normalized", "endpoint": { "uri": "http://quantumleap:8668/v2/notify", "accept": "application/json", } }, "throttling": 10, "@context": "http://context:3000/data-models/ngsi-context.jsonld" }

How to solve this problem? I am following this tutorial text

[c0c0n3]

Hi @tonyrosset :-)

The docs are out of date, sorry about that. But I think the solution to your problem could be straightforward: update to the latest QL and use the NGSILD-Tenant header instead of the NGSI-v2 fiware-service header.

Please have a look at #728 for the details, specifically this comment

• https://github.com/orchestracities/ngsi-timeseries-api/issues/728#issuecomment-1564688224

Let me know if that works for you and we can close this issue.

[SBlechmann]

Sorry for shooting from the side again :'D just saw that issue.

If I'm not mistaken, the support for Linked Data is not in the latest image (0.8.3) but rather merged in the master branch. So you have to build the image yourself from the current master.

[c0c0n3]

hahaha, no worries :-)

yep, the latest versioned image is 0.8.3 which does not include #721---NGSI LD tenant header support. But the latest image we pushed

• orchestracities/quantumleap:edge

does include that feature. So sorry for the confusion, but please have a look at #728 for the details.

[c0c0n3]

Also, we should be releasing a new official versioned image, probably 1.0.0 soon, hopefully before Dec the 6th.

[tonyrosset]

"endpoint": { "uri": "http://quantumleap:8668/v2/notify", "accept": "application/json", "receiverInfo": [ { "key": "fiware-service", "value": "openiot" } ] }

its solved by adding the servicepath in receiverinfo