2018-04-20 18:05|CREATED monitor | # answers= 0, accepted answer= False

Hi Veronika,

That’s a question from Jason, that should be responded by the Orion Developers but I think is better to assign it to Jason. Please could you add an account for Jason in Jira and reassign this issue to him?

Jason, probably would need to provide a functest to Ken, in cc showing what is failing.

Ken, Jason, please could liaise to solve this?

Thanks,

Best

The issue is easy to reproduce within the https://github.com/Fiware/tutorials.Context-Providers <https://github.com/Fiware/tutorials.Context-Providers> GitRepo

1. Pull repository
2. Run ./services stop; ./services create; ./services start;
3. Run the following cUrl commands: - Context Provider is usually localhost:3000. Orion localhost:1026

Check Random Data Generator is Running
curl -X GET \
'http://context-provider/proxy/random/health'

Check Random Data Generator is returning a valid NGSI Array Response
curl -X POST \
'http://context-provider/proxy/random/array/temperature/queryContext' \
-H 'Cache-Control: no-cache' \
-H 'Content-Type: application/json' \
-H 'Postman-Token: b48df54e-7b3a-4406-814b-b978949c4060' \
-d '{
"entities": [

],
"attributes": [
"temperature"
]
}'

Register Random Data Generator as a Context Provider
curl -X POST \
'http://orion/v2/registrations' \
-H 'Cache-Control: no-cache' \
-H 'Content-Type: application/json' \
-H 'Postman-Token: 43ff9fdf-2584-4db9-9b95-bec256fdb7dc' \
-d '{
"description": "Current Customer Count",
"dataProvided": {
"entities": [

],
"attrs": [
"customerCount"
]
},
"provider": {
"http":

,
"legacyForwarding": true
}
}'

Query for Data
curl -X GET \
'http://orion/v2/entities/urn:ngsi-ld:Store:001'

The customerCount has a value of “” - I would expect an array of Lorem Ipsum entries.

Actually I’ve discovered the issue is worse than I thought.

If I have an Entity with an existing object attribute in Orion (e.g.Postal Address)
And then I add in *any* field into the context (e.g. a Number for temperature) then the Object attribute appears as "" when the Entity is requested:

e.g.:

curl -X POST \
'http://localhost:1026/v2/op/update' \
-H 'Content-Type: application/json' \
-g -d '{
"actionType": "APPEND",
"entities": [
{
"id":"urn:ngsi-ld:Store:004","type":"Store",
"address":{"type":"PostalAddress","value":{"streetAddress":"Panoramastraße 1A","addressRegion":"Berlin","addressLocality":"Mitte","postalCode":"10178"}},
"location":{"type":"geo:json","value":{"type":"Point","coordinates":[13.4094,52.5208]}},
"name":

}
]
}’

curl -X POST \
'http://localhost:1026/v2/registrations' \
-H 'Cache-Control: no-cache' \
-H 'Content-Type: application/json' \
-d '{
"description": "Relative Humidity Context Source",
"dataProvided": {
"entities": [

],
"attrs": [
"temperature"
]
},
"provider": {
"http":

,
"legacyForwarding": true
}
}’

curl -X GET \
'http://localhost:1026/v2/entities/urn:ngsi-ld:Store:004'

Response:

{
"id": "urn:ngsi-ld:Store:004",
"type": "Store",
"address": {
"type": "PostalAddress",
"value": "",
"metadata": {}
},
"location": {
"type": "geo:json",
"value": "",
"metadata": {}
},
"name": {
"type": "Text",
"value": "Tower Trödelmarkt",
"metadata": {}
},
"temperature": {
"type": "Number",
"value": "29",
"metadata": {}
}
}

Postal Address has disappeared.

I would add this to the JIRA ticket, but I don’t have a log-in.

Regards,

Jason.

Taking advice from Ken Zangelin (Telefónica I+D)

• I have created issue: [ https://github.com/telefonicaid/fiware-orion/issues/3162]
• I have branched fiware/orion: https://github.com/jason-fox/fiware-orion/tree/feature/3162-func-test
• I have attempted to create a functional test : https://github.com/jason-fox/fiwre-orion/blob/feature/3162-func-test/test/functionalTest/cases/3162_context_providers_legacy_non_primitive/query_for_arrays.test
  + I have no idea if it will run (since I didn’t find out how to invoke the tests)
  + The test is expected to fail on points 06, 08 and 09 since arrays aren’t being returned.
• I have created a pull request: https://github.com/telefonicaid/fiware-orion/pull/3163

This appears to be an Orion bug rather than a Stack Overflow issue.

Bug ticket raised here.

Once the bug is fixed I will self-answer my question on Stack Overflow