Hi Tian, I like this abstraction. I support to expose some interfaces for users to manipulate the "device".
Further, maybe we could introduce the "database", "table", "column" concepts in IoTDB. Best, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -----原始邮件----- > 发件人: "Tian Jiang (JIRA)" <[email protected]> > 发送时间: 2019-08-14 10:23:00 (星期三) > 收件人: [email protected] > 抄送: > 主题: [jira] [Created] (IOTDB-163) Support create device template and create > device. > > Tian Jiang created IOTDB-163: > -------------------------------- > > Summary: Support create device template and create device. > Key: IOTDB-163 > URL: https://issues.apache.org/jira/browse/IOTDB-163 > Project: Apache IoTDB > Issue Type: Improvement > Reporter: Tian Jiang > > > In the present version, it is a little trouble some to create a set > timeseries that has the same measurements. On the other hand, although we use > the conception "device" in the code, it is not properly abstracted. > > Expected usage: > > Using IoTDB in a more _*relational*_ way: > > *CREATE DEVICE TEMPLATE vehicle (speed DOUBLE PLAIN, direction* *DOUBLE > PLAIN, temperature* *DOUBLE PLAIN, fuel* *DOUBLE PLAIN******)* > > If all datatypes(or encodings) are the same, you can write the equal form: > > *CREATE DEVICE TEMPLATE vehicle MEASUREMENTS (speed, direction, temperature, > fuel) DATATYPE DOUBLE ENCODING PLAIN* > > Then you will be able to create time series in an easier way: > > *CREATE DEVICE (vehicle) root.sg1.vehicle1* > > Which equals: > > *CREATE TIMESERIES root.sg1.vehicle1.speed WITH > DATATYPE=DOUBLE,ENCODING=PLAIN* > > *CREATE TIMESERIES root.sg1.vehicle1.direction WITH > DATATYPE=DOUBLE,ENCODING=PLAIN* > > *CREATE TIMESERIES root.sg1.vehicle1.fuel WITH DATATYPE=DOUBLE,ENCODING=PLAIN* > > *CREATE TIMESERIES root.sg1.vehicle1.temperature WITH > DATATYPE=DOUBLE,ENCODING=PLAIN* > > I ** hope this will narrow the gap of using IoTDB and traditional relation > databases. > > > > -- > This message was sent by Atlassian JIRA > (v7.6.14#76016)
