[Fiware-tech-help] [frontierCities2]

[Ailema Vázquez García]

We have created a Context Provider that exposes an NGSI api with the
following entry points
url (r '^ queryContext', views.queryContext.as_view ()),
url (r '^ updateContext', views.updateContext.as_view ()),

Starting from the fact that we have registered an entity in Orion, and we
verify that it is actually in the table registrations of the database.

If we try to execute the following queries to obtain the information, we
obtain it correctly. Checking that Orion has registered them with our
supplier and forwards the query to it.
GET /v1/contextEntities/5b43f945ccfc0348246283dc
GET /v2/entities/5b43f945ccfc0348246283dc

But, if we execute any of the following queries to update the data of the
entity, they do not redirect to the Context Provider, and we obtain the
following answers.
PUT /v1/contextEntities/5b43f945ccfc0348246283dc/attributes
{
    "errorCode": {
        "code": "404",
        "reasonPhrase": "No context element found",
        "details": "5b43f945ccfc0348246283dc"
    }
}
PATCH /v2/entities/5b43f945ccfc0348246283dc/attrs
{
    "error": "NotFound",
    "description": "The requested entity has not been found. Check type and
id"
}

The only way we have been able to update the information is through the
following query, which redirects correctly and updates.
POST /v1/updateContext
We were wondering if we are avoiding something so that just like when we
consult the information, the update works well regardless of the query that
is executed.

Regards
I am aware
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20180710/9f27bf11/attachment.html>