ALIGN BY DEVICE: the data types of the same measurement column should be the same across devices.

[Trevor Hart]

Hello Team



I have a customer using my application with IoTDB 1.3.0 in the backend.



Auto create schema is enabled as there is no fixed template. Multiple devices 
are pushing data to IotDB.



I have seen some ALIGN BY DEVICE queries fail with the error in the subject ie



ALIGN BY DEVICE: the data types of the same measurement column should be the 
same across devices.



The "show timeseries" shows that from one device the value has been inferred as 
FLOAT and another as DOUBLE.


Per the documentation it is suggested that the default 
"floating_string_infer_type" is DOUBLE but that is not what I am seeing. Why am 
I getting FLOAT? Is the default "floating_string_infer_type" not being honoured?



Currently in the config file "floating_string_infer_type" is commented out. 
Should I explicitly set this to DOUBLE?


Thanks 

Trevor Hart

IoTDB quarter report (2024 Q2)

[Xiangdong Huang]

Hi all,

This is the draft of IoTDB quarter report

## 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

## Project Status:
Current project status: Ongoing with high activity.
Issues for the board:
- there are some trademark issues but the community has resolved them.

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

Community changes, past quarter:
- No new PMC members. Last addition was Steve Yurong Su on 2023-09-28.
- William Song was added as committer on 2024-03-22
- Caiyin Yang was added as committer on 2024-06-12

## Project Activity:
- Recent releases:
IOTDB-1.3.2 is on the way.
IOTDB-1.3.1 was released on 2024-04-22.
IOTDB-1.3.0 was released on 2024-01-01.
IOTDB-1.2.2 was released on 2023-10-15.

- Main work of project:
* We are working on the table model providing data to users in a table view
in the same way as relational databases which will greatly reduce the
learning curve of IoTDB.
* Collaborate with the Apache StreamPipes community to improve the IoTDB plugin
 and explore other means on integration.
* New query optimization rules are added to greatly improve the query
performance of IoTDB, like PredicatePushDown and AggregatePushDown.
* Explain Analyze tool which can be used to analyze specific query
performance better and is a good tool for troubleshooting performance problems


## Community Health:
Overall community health is good.
- Joined  "Digital Economy-Urban Open Source Tour"  meetup in Shanghai.
- the mailing list traffic increases (226 emails compared to 76)

Best,
---
Xiangdong Huang

Re: IoTDB quarter report (2024 Q2)

[Jialin Qiao]

Looks good!

Jialin Qiao

Xiangdong Huang  于2024年6月12日周三 09:11写道：
>
> Hi all,
>
> This is the draft of IoTDB quarter report
>
> ## 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
>
> ## Project Status:
> Current project status: Ongoing with high activity.
> Issues for the board:
> - there are some trademark issues but the community has resolved them.
>
> ## Membership Data:
> Apache IoTDB was founded 2020-09-16 (4 years ago)
> There are currently 63 committers and 29 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Steve Yurong Su on 2023-09-28.
> - William Song was added as committer on 2024-03-22
> - Caiyin Yang was added as committer on 2024-06-12
>
> ## Project Activity:
> - Recent releases:
> IOTDB-1.3.2 is on the way.
> IOTDB-1.3.1 was released on 2024-04-22.
> IOTDB-1.3.0 was released on 2024-01-01.
> IOTDB-1.2.2 was released on 2023-10-15.
>
> - Main work of project:
> * We are working on the table model providing data to users in a table view
> in the same way as relational databases which will greatly reduce the
> learning curve of IoTDB.
> * Collaborate with the Apache StreamPipes community to improve the IoTDB 
> plugin
>  and explore other means on integration.
> * New query optimization rules are added to greatly improve the query
> performance of IoTDB, like PredicatePushDown and AggregatePushDown.
> * Explain Analyze tool which can be used to analyze specific query
> performance better and is a good tool for troubleshooting performance problems
>
>
> ## Community Health:
> Overall community health is good.
> - Joined  "Digital Economy-Urban Open Source Tour"  meetup in Shanghai.
> - the mailing list traffic increases (226 emails compared to 76)
>
> Best,
> ---
> Xiangdong Huang

Re: ALIGN BY DEVICE: the data types of the same measurement column should be the same across devices.

[Jialin Qiao]

Hi,

We just changed the default infer type of integer and floating to
DOUBLE [1], it will be released in 1.3.2.

For <=1.3.1, you could explicitly set this to DOUBLE.

[1] https://github.com/apache/iotdb/pull/12223

Jialin Qiao

Trevor Hart  于2024年6月12日周三 06:41写道：
>
> Hello Team
>
>
>
> I have a customer using my application with IoTDB 1.3.0 in the backend.
>
>
>
> Auto create schema is enabled as there is no fixed template. Multiple devices 
> are pushing data to IotDB.
>
>
>
> I have seen some ALIGN BY DEVICE queries fail with the error in the subject ie
>
>
>
> ALIGN BY DEVICE: the data types of the same measurement column should be the 
> same across devices.
>
>
>
> The "show timeseries" shows that from one device the value has been inferred 
> as FLOAT and another as DOUBLE.
>
>
> Per the documentation it is suggested that the default 
> "floating_string_infer_type" is DOUBLE but that is not what I am seeing. Why 
> am I getting FLOAT? Is the default "floating_string_infer_type" not being 
> honoured?
>
>
>
> Currently in the config file "floating_string_infer_type" is commented out. 
> Should I explicitly set this to DOUBLE?
>
>
> Thanks
>
> Trevor Hart

Re: ALIGN BY DEVICE: the data types of the same measurement column should be the same across devices.

[Trevor Hart]

Ah that is great to hear! Thank you!




Thanks 

Trevor Hart




 On Wed, 12 Jun 2024 13:50:43 +1200 Jialin Qiao  
wrote ---



Hi, 
 
We just changed the default infer type of integer and floating to 
DOUBLE [1], it will be released in 1.3.2. 
 
For <=1.3.1, you could explicitly set this to DOUBLE. 
 
[1] https://github.com/apache/iotdb/pull/12223 
 
Jialin Qiao 
 
Trevor Hart  于2024年6月12日周三 06:41写道： 
> 
> Hello Team 
> 
> 
> 
> I have a customer using my application with IoTDB 1.3.0 in the backend. 
> 
> 
> 
> Auto create schema is enabled as there is no fixed template. Multiple devices 
> are pushing data to IotDB. 
> 
> 
> 
> I have seen some ALIGN BY DEVICE queries fail with the error in the subject 
> ie 
> 
> 
> 
> ALIGN BY DEVICE: the data types of the same measurement column should be the 
> same across devices. 
> 
> 
> 
> The "show timeseries" shows that from one device the value has been inferred 
> as FLOAT and another as DOUBLE. 
> 
> 
> Per the documentation it is suggested that the default 
> "floating_string_infer_type" is DOUBLE but that is not what I am seeing. Why 
> am I getting FLOAT? Is the default "floating_string_infer_type" not being 
> honoured? 
> 
> 
> 
> Currently in the config file "floating_string_infer_type" is commented out. 
> Should I explicitly set this to DOUBLE? 
> 
> 
> Thanks 
> 
> Trevor Hart

Introduction of Enhanced Load Functionality with Multi-Drive Support

[ITAMI SHO]

Hello everyone,

My name is Itami Sho, a contributor to IoTDB, and I am excited to share with 
you a recent enhancement I have implemented in our Load functionality. This 
optimization introduces support for multiple drive letters during the second 
phase of Load functionality to store TsFile PieceNode.

Previously, the Load feature only supported PieceNode storing on a single drive 
letter. However, in environments with multi-drive clusters, this limitation 
could lead to performance bottlenecks. To address this issue, I have optimized 
the Load functionality to support multiple drive letters, significantly 
improving overall performance in such scenarios.

You can review the details of my implementation in the following PR:
https://github.com/apache/iotdb/pull/12675

Best regards,
Itami Sho