[Backlogmanager] [FIWARE-JIRA] (HELP-13314) [fiware-stackoverflow] Can' t store attribute' s value with properly type using IoTAgentUL

[Jose Gato Luis (JIRA)]

     [ https://jira.fiware.org/browse/HELP-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jose Gato Luis updated HELP-13314:
----------------------------------
    Status: Impeded  (was: In Progress)

> [fiware-stackoverflow] Can't store attribute's value with properly type using IoTAgentUL
> ------------------------------------------------------------------------------------------------
>
>                 Key: HELP-13314
>                 URL: https://jira.fiware.org/browse/HELP-13314
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Jose Gato Luis
>              Labels: fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 05-07-2017 at 16:07
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/44928815/cant-store-attributes-value-with-properly-type-using-iotagentul
> +Question:+
> Can't store attribute's value with properly type using IoTAgentUL
> +Description:+
> I need to store the values of devices' attributes with the right type in OrionCB's MongoDB.
> As I was unable to perform that I dived into the code and found that IoTAgentUL (as well as IoTAgentJSON) uses OrionCB's API v1 instead of API v2.
> As I can see API v1's updateContext sends data to MongoDB without it's type, so every measure is stored as text.
> In the other hand I found that API v2's update entity send data to MongoDB with it's type. It produces that I can store attribute's values with it's type which benefits me when manipulating data (i.e. creating indexes, sorting, etc).
> My question is if is there any workaround to solve this using the current implementations of IoT Agents.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)