Environment
orion-ld:1.6.0
mongo:3.6
Description
We are using orion-ld in an environment where there are components using the V2 part and others using the LD part.
Recently we realised that when we have both ‘V2-type’ and ‘LD-type’ subscriptions in the same NGSI-Tenant, the call to /v2/subscriptions throws an exception that crashes orion-ld.
The error output is:
terminate called after throwing an instance of ‘mongo::MsgAssertionException’ what(): wrong type for field (_id) 2 != 7
In the same NGSI-Tenant, the call to the LD endpoint is executed correctly.
If no LD subscriptions are present the V2 endpoint responds correctly.
Environment
orion-ld:1.6.0
mongo:3.6
Description
We are using orion-ld in an environment where there are components using the V2 part and others using the LD part.
Recently we realised that when we have both ‘V2-type’ and ‘LD-type’ subscriptions in the same NGSI-Tenant, the call to /v2/subscriptions throws an exception that crashes orion-ld.
The error output is:
terminate called after throwing an instance of ‘mongo::MsgAssertionException’ what(): wrong type for field (_id) 2 != 7In the same NGSI-Tenant, the call to the LD endpoint is executed correctly.
If no LD subscriptions are present the V2 endpoint responds correctly.