You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Julian Feinauer (Jira)" <ji...@apache.org> on 2020/06/12 10:45:00 UTC

[jira] [Assigned] (IOTDB-742) Add Support for structured Messages, e.g. in JSON format

     [ https://issues.apache.org/jira/browse/IOTDB-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Feinauer reassigned IOTDB-742:
-------------------------------------

    Assignee: Julian Feinauer

> Add Support for structured Messages, e.g. in JSON format
> --------------------------------------------------------
>
>                 Key: IOTDB-742
>                 URL: https://issues.apache.org/jira/browse/IOTDB-742
>             Project: Apache IoTDB
>          Issue Type: New Feature
>            Reporter: Julian Feinauer
>            Assignee: Julian Feinauer
>            Priority: Major
>
> Currently IoTDB Supports only primitives which are stored in a single measurement. If we would add a "logical" layer on top we could just split each JSON message into its primitives and store it accordingly. If the message is not nested but only key-value pair this is simply a "syntactic sugar".
> Consider the following IoTDB Command:
> {code:sql}
> INSERT INTO root.demo.cars.mycar (time, json) VALUES (NOW(), "{\"speed\": 100, \"color\": \"red\"}")
> {code}
> It uses the word "json" as colum name which indicates that it wants to store a json. Thus IoTDB should store the data from the json and this is equivalent to the normal syntax
> {code:sql}
> INSERT INTO root.demo.cars.mycar (time, speed, color) VALUES (NOW(), 100, "red")
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)