-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't figure out "Nested arrays are not supported" error #322
Comments
this is not recognised as geo:json. rename consider that ql supports ngsi-v2, but no ngsi-ld, so, when the message arrives, the value:
is processed as an array (not as geo:json). but being a nested array, which is not supported by CrateDB, things go badly this is a guess though :) i may be wrong. |
Thanks to pointing out that detail, I took the NGSI-LD Sample and adopted it to more fit NGSIv2 but missed the "GeoProperty" You are perfectly right, reformated my Context and recreated the tables, now it works like a charm again. Thank you very much! |
happy to have helped :) |
For the sake of completeness, this issue is related to #343. In fact, the
|
Our orion-context broker gets Weather and Weather Forecast data following more or less the smart-data-model specification (its in a state between NGSIv2 and NGSI-LD).
Our WeatherObserved Entities look like this, for example
Subscribing QuantumLeap to this created the tables
etweatherobserved
andetweatherforecast
but does not append rows. The QuanumLeap logs sayI can't figure out on which part of the JSON this message is refering to, as we also utilize the Device smart-data-model where I really use a List/Array as Value which works perfectly like a charm.
The text was updated successfully, but these errors were encountered: