Re: IoTDB schema to relational schema discussion

[Eric Pai]

Wow, I think this is very interesting to link relational model to our 
timeseries model.
Could you give some examples about how to map timeseries to tables and columns? 
In my brief study about Druid, it seems that for a particular measurement of 
thousands of devices, it may be a wild table with amount of columns?

在 2022/6/4 16:25，“陈振宇” 写入:

I know the community has discussed several times about how to let IoTDB 
support standard SQL [1]. A naive perspective is that if we can convert IoTDB 
into a relational table schema, then we can use the ability of standard SQL to 
represent richful query semantics. 
The current idea is to take reference in Apache Druid, which allows users 
define which column represents for the timestamp, which columns are dimensions 
(equals to iotdb's time series path, except for the last level of the path), 
and which are metrics (equals to iotdb's measurement)[2].
If there is such an interface to let users define the above info (Druid 
uses a json to define that), then it is possible to transform the schema of 
IoTDB into a relational model. This would further optimize the Apache Calcite 
integration work previously attempt by the community, and enrich the query 
capacity of IoTDB.
[1] 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fgwrm4rly3jsz7zyxm8bwhr1yy4g13x65data=05%7C01%7C%7Cdc83a45018b34784cbeb08da4603d631%7C84df9e7fe9f640afb435%7C1%7C0%7C63789927996385%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=Qa361I1PeFQOC%2F2mxI6BTGUSeAkBrRb2krgZsahTViw%3Dreserved=0
[2] 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdruid.apache.org%2Fdocs%2F0.22.1%2Fingestion%2Fschema-design.html%23time-series-modeldata=05%7C01%7C%7Cdc83a45018b34784cbeb08da4603d631%7C84df9e7fe9f640afb435%7C1%7C0%7C63789927996385%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=DZDQPZUliOnsMwCzrOD%2Fq9p%2FKFHPR3Z1GC7rys7eyi8%3Dreserved=0

Re:IoTDB quarterly report draft

[????????]

Guanfei Guo
guoguan...@qq.com







--Original--
From:   
 "dev"  
  

回复: JDBC vs Java API

[冯 庆新]

Hello Trevor Hart

Can you access this web link: 
http://111.202.73.147:13000/d/5ZvuEYE7z/atm-biao-zhun-da-qi-ya-huan-jing?orgId=1=26
Is this one ok?

Config items in benchmark:
DB_SWITCH=IoTDB-013-JDBC  / SESSION_BY_TABLET / SESSION_BY_RECORDS / 
SESSION_BY_RECORD
GROUP_NUMBER=10
LOOP=1000
DEVICE_NUMBER=50
SENSOR_NUMBER=500
BATCH_SIZE_PER_WRITE=100
POINT_STEP=1000
OP_INTERVAL=0
IS_OUT_OF_ORDER=false

B.R
qingxin.feng


发件人: Trevor Hart
发送时间: 2022年6月6日 8:46
收件人: dev
主题: JDBC vs Java API

Hello Team



Does anyone have any published benchmark results of JDBC vs the Java API?



Firstly Im aware of https://github.com/thulab/iotdb-benchmark but I dont see 
any published results for the various API methods.



I currently use JDBC for my non-realtime ingestion of data and while Ive never 
encountered any bottle necks I am aware that the documentation says that JDBC 
is not recommended for high velocity data.



Ive done some very basic ingestions benchmarking tests of inserting 1 million 
rows and the Java API is around 2x faster. Is this the typical improvement 
between JDBC and Java API?



For my simplistic test I am inserting 1 millions rows of timestamp & 
incrementing row id eg  insert into root.sg1.d1(timestamp,s1) 
values(${DateTime.Now}, ${n})



With JDBC I get around 6000 rows per second.



With the Java native API I get around 12000 rows per second using 
session.executeNonQueryStatement.



I assume insertTablets and insertRecord(s) would be even faster?



Thanks

Trevor Hart

JDBC vs Java API

[Trevor Hart]

Hello Team



Does anyone have any published benchmark results of JDBC vs the Java API?



Firstly Im aware of https://github.com/thulab/iotdb-benchmark but I dont see 
any published results for the various API methods.



I currently use JDBC for my non-realtime ingestion of data and while Ive never 
encountered any bottle necks I am aware that the documentation says that JDBC 
is not recommended for high velocity data.



Ive done some very basic ingestions benchmarking tests of inserting 1 million 
rows and the Java API is around 2x faster. Is this the typical improvement 
between JDBC and Java API?



For my simplistic test I am inserting 1 millions rows of timestamp & 
incrementing row id eg  insert into root.sg1.d1(timestamp,s1) 
values(${DateTime.Now}, ${n})



With JDBC I get around 6000 rows per second.



With the Java native API I get around 12000 rows per second using 
session.executeNonQueryStatement.



I assume insertTablets and insertRecord(s) would be even faster?



Thanks

Trevor Hart

IoTDB quarterly report draft

[Xiangdong Huang]

Hi all,

Pls review the report draft, and supply whatever you think we should report.
I will submit it on Jun 8th.

## Description:
The mission of Apache IoTDB is the creation and maintenance of software
related
to an IoT native database with high performance for data management and
analysis

## Issues:

There are no issues requiring board attention.


## Membership Data:
Apache IoTDB was founded 2020-09-16 (2 years ago)
There are currently 49 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- Yuan Tian was added to the PMC on 2022-04-21
- Minghui Liu was added as committer on 2022-05-25
- Xuxin Liu was added as committer on 2022-05-25
- Qijun Xie was added as committer on 2022-05-28
- Yukun Zhou was added as committer on 2022-05-25

## Project Activity:

Recent releases:
- IOTDB-0.13.0 was released on 2022-03-20.
- IoTDB-0.12.5 was released on 2022-03-08.

there are some bugs are found and fixed after the two versions were
release.
We will keep to maintain v0.12.x and v0.13.x until v0.14 is released and
v0.13.x is relatively stable.

The community is developing the new cluster version, which may be finished
in the later 1-2 months.


## Community Health:

In summary, the community is more and more diverse and active.

There are about 90 code contributors in the past quarter,
and we have 189 code contributors in total according to Github's statistics.

The community submitted several topics to ApacheCon Asia,
but missed the Apachecon NA.


Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

Call reviewers for iotdb-web-workbench

[Xiangdong Huang]

Hi all,

I noticed that the iotdb-web-workbench repo lacks reviews.

* Welcome all contributors ( no matter whether you are the committer) who
are familiar with
Vue3.0 and Spring technologies.

* The Committers and PMCs should pay more attentions on this repo as there
are many works left to guarantee the repo is in compliance with ASF project.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University