CVE-2022-43766: Apache IoTDB: ReDoS Vulnerability by REGEXP

[Haonan Hou]

Severity: low

Description:

Apache IoTDB version 0.12.2 to 0.12.6, 0.13.0 to 0.13.2 are vulnerable by the 
attack of REGEXP query with Java8. Users should upgrade to 0.13.3 which 
addresses this issue or use a later version of Java to avoid it.

Change of configuration files

[Haonan Hou]

Hi,

In IoTDB 1.0, we have two roles of nodes and two major configuration files, 
iotdb-datanode.properties
and iotdb-confignode.properties. Some configurations are duplicated in these 
files such as the admin 
username and password.

Therefore, we are going to add a new configuration file, 
iotdb-common.properties, to solve this problems
The design doc is [1].

[1] https://apache-iotdb.feishu.cn/docx/doxcnjzB2xd9sScIlkNYJUJA1zb


Thanks,
Haonan Hou

Re: Change of configuration files

[Haonan Hou]

One more change I would like to mentions. I will remove the configurations of 
HDFS, since we
do not recommend users to use it on IoTDB.

Best,
Haonan Hou

> On Oct 28, 2022, at 5:13 PM, Haonan Hou  wrote:
> 
> Hi,
> 
> In IoTDB 1.0, we have two roles of nodes and two major configuration files, 
> iotdb-datanode.properties
> and iotdb-confignode.properties. Some configurations are duplicated in these 
> files such as the admin 
> username and password.
> 
> Therefore, we are going to add a new configuration file, 
> iotdb-common.properties, to solve this problems
> The design doc is [1].
> 
> [1] https://apache-iotdb.feishu.cn/docx/doxcnjzB2xd9sScIlkNYJUJA1zb
> 
> 
> Thanks,
> Haonan Hou

Unify thread num configurations to thread_count

[Haonan Hou]

Hi,

I submit a PR[1] to rename all thread num configurations to thread_count. 

- rpc_selector_thread_num -> rpc_selector_thread_count
- selector_thread_nums_of_client_manager -> 
selector_thread_count_of_client_manager 
- procedure_core_worker_thread_size -> procedure_core_worker_thread_count
- continuous_query_submit_thread -> continuous_query_submit_thread_count
- concurrent_flush_thread -> flush_thread_count
- concurrent_query_thread -> query_thread_count
- concurrent_sub_rawQuery_thread -> sub_rawQuery_thread_count
- upgrade_thread_num -> upgrade_thread_count
- concurrent_compaction_thread -> compaction_thread_count
- sub_compaction_thread_num -> sub_compaction_thread_count
- concurrent_window_evaluation_thread -> window_evaluation_thread_count

For details, see[2]. 

[1] https://github.com/apache/iotdb/pull/7817
[2] https://apache-iotdb.feishu.cn/docx/doxcnjzB2xd9sScIlkNYJUJA1zb

Best,
Haonan Hou

Re: Chaneg the name of StandAloneConsensus

[Haonan Hou]

+1 for SimpleConsensus.

Cassandra has a similar `SimpleStrategy`. 
See 
https://cassandra.apache.org/doc/4.1/cassandra/architecture/dynamo.html#simple-strategy

Best,
Haonan Hou

> On Oct 31, 2022, at 9:32 PM, Jialin Qiao  wrote:
> 
> +1 for OneReplicaConsensus
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> Yuan Tian  于2022年10月31日周一 20:08写道：
>> 
>> Hi all,
>> 
>> After discussing, we think OneCopyConsensus may be better. So I rename
>> it to OneCopyConsensus in this pr
>> https://github.com/apache/iotdb/pull/7832/files
>> 
>> Best,
>> 
>> Yuan Tian
>> 
>> On Mon, Oct 31, 2022 at 12:39 PM Yuan Tian  wrote:
>>> 
>>> Hi, all
>>> 
>>> Now, we name the consensus which is optmized for only single
>>> replica(actualy this consensus can only support one replica) as
>>> StandAloneConsensus. However, `StandAlone` is ambiguous, it was used
>>> for IoTDB StandAlone version(v.s. distributed version).
>>> 
>>> So, we decided to change its name, here are some candidates:
>>> 
>>> 1. OneCopyConsensus
>>> 2. NoCopyConsensus
>>> 3. SimpleConsensus
>>> 4. ZereCostConsensus
>>> 
>>> Do you guys have any suggestions? Or Which one of the above names you voted 
>>> for?
>>> 
>>> 
>>> Best,
>>> --
>>> Yuan Tian

Re: Chaneg the name of StandAloneConsensus

[Haonan Hou]

+1 for SimpleConsensus.

Cassandra has a similar `SimpleStrategy`. 
See 
https://cassandra.apache.org/doc/4.1/cassandra/architecture/dynamo.html#simple-strategy

Best,
Haonan Hou

> On Oct 31, 2022, at 9:32 PM, Jialin Qiao  wrote:
> 
> +1 for OneReplicaConsensus
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> Yuan Tian  于2022年10月31日周一 20:08写道：
>> 
>> Hi all,
>> 
>> After discussing, we think OneCopyConsensus may be better. So I rename
>> it to OneCopyConsensus in this pr
>> https://github.com/apache/iotdb/pull/7832/files
>> 
>> Best,
>> 
>> Yuan Tian
>> 
>> On Mon, Oct 31, 2022 at 12:39 PM Yuan Tian  wrote:
>>> 
>>> Hi, all
>>> 
>>> Now, we name the consensus which is optmized for only single
>>> replica(actualy this consensus can only support one replica) as
>>> StandAloneConsensus. However, `StandAlone` is ambiguous, it was used
>>> for IoTDB StandAlone version(v.s. distributed version).
>>> 
>>> So, we decided to change its name, here are some candidates:
>>> 
>>> 1. OneCopyConsensus
>>> 2. NoCopyConsensus
>>> 3. SimpleConsensus
>>> 4. ZereCostConsensus
>>> 
>>> Do you guys have any suggestions? Or Which one of the above names you voted 
>>> for?
>>> 
>>> 
>>> Best,
>>> --
>>> Yuan Tian

Re: [VOTE] Create a repo for TsFile-Viewer

[Haonan Hou]

+1

Haonan Hou

> On Nov 7, 2022, at 10:00 AM, Jialin Qiao  wrote:
> 
> Hi,
> 
> Here is a Tool for viewing TsFile: https://github.com/apache/iotdb/pull/6995
> 
> As TsFile-Viewer could be used independently, it could be a separate
> repository for users.
> 
> So, I'd like to start a vote for creating a new Repo for TsFile-Viewer.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> The vote is open for the next 72 hours and passes if at least three +1
> votes and more +1 votes than -1 votes.
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC

Re: [VOTE] Create a repo for TsFile-Viewer

[Haonan Hou]

+1

Haonan Hou

> On Nov 7, 2022, at 10:00 AM, Jialin Qiao  wrote:
> 
> Hi,
> 
> Here is a Tool for viewing TsFile: https://github.com/apache/iotdb/pull/6995
> 
> As TsFile-Viewer could be used independently, it could be a separate
> repository for users.
> 
> So, I'd like to start a vote for creating a new Repo for TsFile-Viewer.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> The vote is open for the next 72 hours and passes if at least three +1
> votes and more +1 votes than -1 votes.
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC

Re: [VOTE] Usage of Apache IoTDB Logo as Stickers for A Meetup

[Haonan Hou]

+1

Haonan Hou

> On Nov 26, 2022, at 8:50 AM, Jialin Qiao  wrote:
> 
> +1
> Glad to see a meetup in Germany~
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> Pengcheng Zheng  于2022年11月25日周五 00:11写道：
>> 
>> Hi Xiangdong,
>> 
>> Yes the agenda is planned as followed:
>> 18:00 - 18:10 Warm-up: Get to know each other
>> 18:10 - 18:15 Welcome
>> 18:15 - 19:00 Talk by Julian Feinauer: "Introduction to Apache IoTDB"
>> 19:15 - 20:00 Talk by Tim Mitsch: "Using IoTDB for high-volume energy data"
>> 20:00 - 21:00 Informal networking: Drink, food, snack & mingle
>> 
>> More details of the meetup is to be found under [1].
>> 
>> 
>> [1] https://www.meetup.com/de-DE/apache-iotdb-meetup/events/289831235/
>> 
>> Best regards,
>> Pengcheng
>> 
>> Am Do., 24. Nov. 2022 um 15:43 Uhr schrieb Xiangdong Huang 
>> :
>>> 
>>> +1 for printing IoTDB stickers.
>>> BTW, is there a schedule?
>>> Best.
>>> ---
>>> Xiangdong Huang
>>> School of Software, Tsinghua University
>>> 
>>> 黄向东
>>> 清华大学 软件学院
>>> 
>>> Pengcheng Zheng  于2022年11月24日周四 01:21写道：
>>>> 
>>>> Hi all,
>>>> 
>>>> Since we have quite a few users and contributors of Apache IoTDB in
>>>> Germany now, we would like to gather up on 08 Dez 2022 as the "First
>>>> German Apache IoTDB User Group Meeting" and a party shortly before
>>>> Christmas :). Details of the meetup could be found under [1].
>>>> 
>>>> We have designed a roll-up of IoTDB for the meetup. The file could be
>>>> found under [2], and the size is 85*200cm with bleed.
>>>> 
>>>> Additionally, Timecho as the sponsor for the meetup wants to print out
>>>> some of the Apache IoTDB stickers to hand out (just the IoTDB Logo),
>>>> for which the usage need to be voted. I will send a mail to
>>>> tradema...@apache.org if it is approved.
>>>> 
>>>> Please vote accordingly:
>>>> [ ] +1 approve
>>>> [ ] +0 no opinion
>>>> [ ] -1 disapprove with the reason
>>>> 
>>>> The vote is open for the next 72 hours and passes with at least three +1
>>>> votes and more +1 votes than -1 votes.
>>>> 
>>>> 
>>>> [1] https://www.meetup.com/de-DE/apache-iotdb-meetup/events/289831235/
>>>> [2] https://timechor.feishu.cn/file/boxcnVwjP4Ugd4EKTESW96BrHxh
>>>> 
>>>> 
>>>> Best regards,
>>>> 
>>>> Pengcheng Zheng
>>>> Timecho

[VOTE] Apache IoTDB 1.0.0 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
and cluster mode.

Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: 1.0.0
Hash for the release tag: dffb1d9470597cbe6cfba9a3d0272ab4ddaf8f0f

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1089
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc1/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.0.0 RC1 release

[Haonan Hou]

Alright, let me release RC2.

Haonan Hou

> On Nov 30, 2022, at 11:38 PM, Jialin Qiao  wrote:
> 
> -1
> 
> Cross-space compaction is an important feature. but it is not enabled due to 
> IOTDB-5092 in RC1.
> Currently, this is fixed and we add more checks.
> 
> Thanks,
> Jialin Qiao
> 
> 
> On 2022/11/29 20:25:55 Haonan Hou wrote:
>> Hi all,
>> 
>> Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
>> and cluster mode.
>> 
>> Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
>> on accepting it for release.  All Maven artifacts are available under [1].
>> Voting will be open for 72hr.
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> are required to pass.
>> 
>> Release tag: 1.0.0
>> Hash for the release tag: dffb1d9470597cbe6cfba9a3d0272ab4ddaf8f0f
>> 
>> Before voting +1, PMC members are required to download
>> the signed source code package, compile it as provided, and test
>> the resulting executable on their own platform, along with also
>> verifying that the package meets the requirements of the ASF policy
>> on releases. [3]
>> 
>> You can achieve the above by following [4].
>> 
>> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM 
>> items in [4])
>> [ ]  -1 reject (explanation required)
>> 
>> 
>> [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1089
>> [2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc1
>> [3] https://www.apache.org/dev/release.html#approving-a-release
>> [4] 
>> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>> [5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc1/RELEASE_NOTES.md
>> [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 
>> 
>> Best,
>> 
>> Haonan Hou

[VOTE] Apache IoTDB 1.0.0 RC2 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
and cluster mode.

Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.0.0
Hash for the release tag: 4d0b3af94edd57df9115dbf56487a906bee187ae

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1090
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc2
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc2/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.0.0 RC2 release

[Haonan Hou]

Sure, let me do RC3 releasing.

Haonan Hou

> On Dec 1, 2022, at 12:09 PM, Jialin Qiao  wrote:
> 
> Sorry for -1 again
> 
> RC2 also has NPE in cross space compaction, which is fixed in 
> https://github.com/apache/iotdb/pull/8277
> 
> We could start RC3
> 
> Jialin Qiao
> 
> 
> On 2022/11/30 17:23:51 Haonan Hou wrote:
>> Hi all,
>> 
>> Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
>> and cluster mode.
>> 
>> Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
>> on accepting it for release.  All Maven artifacts are available under [1].
>> Voting will be open for 72hr.
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> are required to pass.
>> 
>> Release tag: v1.0.0
>> Hash for the release tag: 4d0b3af94edd57df9115dbf56487a906bee187ae
>> 
>> Before voting +1, PMC members are required to download
>> the signed source code package, compile it as provided, and test
>> the resulting executable on their own platform, along with also
>> verifying that the package meets the requirements of the ASF policy
>> on releases. [3]
>> 
>> You can achieve the above by following [4].
>> 
>> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM 
>> items in [4])
>> [ ]  -1 reject (explanation required)
>> 
>> 
>> [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1090
>> [2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc2
>> [3] https://www.apache.org/dev/release.html#approving-a-release
>> [4] 
>> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>> [5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc2/RELEASE_NOTES.md
>> [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 
>> 
>> Best,
>> 
>> Haonan Hou

[VOTE] Apache IoTDB 1.0.0 RC3 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
and cluster mode.

Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.0.0
Hash for the release tag: 3ed60f37a6d60dba93dbe46d1fdfc630bf3561b2

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1091
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc3
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc3/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.0.0 RC3 release

[Haonan Hou]

Okey, RC4 will come….

Haonan

> On Dec 1, 2022, at 6:01 PM, Gaofei Cao  wrote:
> 
> -1
> 
> LastFlushTime may be set incorrectly when DataRegion is recovering,
> please see more details in
> IOTDB-5103(https://issues.apache.org/jira/browse/IOTDB-5103) in RC3.
> 
> Thanks,
> Gaofei Cao
> 
> Haonan Hou  于2022年12月1日周四 13:14写道：
>> 
>> Hi all,
>> 
>> Apache IoTDB 1.0.0 version has a new architecture that supports standalone
>> and cluster mode.
>> 
>> Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
>> on accepting it for release.  All Maven artifacts are available under [1].
>> Voting will be open for 72hr.
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> are required to pass.
>> 
>> Release tag: v1.0.0
>> Hash for the release tag: 3ed60f37a6d60dba93dbe46d1fdfc630bf3561b2
>> 
>> Before voting +1, PMC members are required to download
>> the signed source code package, compile it as provided, and test
>> the resulting executable on their own platform, along with also
>> verifying that the package meets the requirements of the ASF policy
>> on releases. [3]
>> 
>> You can achieve the above by following [4].
>> 
>> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM 
>> items in [4])
>> [ ]  -1 reject (explanation required)
>> 
>> 
>> [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1091
>> [2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc3
>> [3] https://www.apache.org/dev/release.html#approving-a-release
>> [4] 
>> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>> [5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc3/RELEASE_NOTES.md
>> [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
>> 
>> Best,
>> 
>> Haonan Hou

[VOTE] Apache IoTDB 1.0.0 RC4 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
and cluster mode.

Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.0.0
Hash for the release tag: ea2fdef0c065b9209fb92215402c5649fa5cac20

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1092
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc4
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc4/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 

Best,

Haonan Hou

[VOTE] Apache IoTDB 1.0.0 RC5 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.0.0 version has a new architecture that supports standalone 
and cluster mode.

Apache IoTDB 1.0.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.0.0
Hash for the release tag: fbbca3ffa3d54b2757c22502f7211b5a2be72c96

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1093
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc5
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.0/rc5/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS 

Best,

Haonan Hou

[RESULT][VOTE] Release Apache IoTDB 1.0.0

[Haonan Hou]

Hi all,

The release is approved by accepting 8 +1 votes:

4 from PMCs,
Jialin Qiao,
Yuan Tian,
Gaofei Cao,
Chao Wang


2 from committers,
HW-Chao Wang,
CloudWise-luke.miao

2 from contributors,
Guanfei Guo,
William Song

Vote threads: 
https://lists.apache.org/thread/q693fy4cgcbor1l30521px41qx6pt7td
https://lists.apache.org/thread/byo1fpkczszvw5g7qf9pjk5szrw8q1s7

Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.0.0 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.0.0.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.0.0 version has a new architecture that supports standalone
and cluster mode.


## New Features

* New architecture that supports standalone and cluster mode with two types of 
nodes: ConfigNode, DataNode
* Support ConfigNode management: Start/Add, Stop, Remove
* Support DataNode management: Start/Add, Stop, Remove
* Support replication of ConfigNode, Schema and Data
* Support Consensus Protocol: Simple, IoT, Ratis
* Support Cluster management sql: show cluster, show regions
* Support administration in Cluster:  User, Permission, Role management
* Support authorization when login and executing a command
* Support create/show/count/delete database
* Support show/count devices
* Support create/show/count timeseries
* Support schema template management
* Support MPP(massively parallel process) framework in cluster
* Support insertion, deletion and all query types in Cluster
* Support CSV import/export tools
* Support TsFile import/export tools
* Support Sync TsFile from an IoTDB with one replica to another with any 
replica number
* Support UDF framework in Cluster
* Support new UDF 'change_points
* Support stateful, stateless Trigger in Cluster
* Support Select into in Cluster
* Support Continuous Query in Cluster
* Support flush on local/cluster
* Support clear cache on local/cluster
* Support metric for DataNode and ConfigNode with output to IoTDB, Prometheus, 
and JMX
* Support DBAPI in python client
* Support RestApi, MQTT for cluster
* Support having clause and between expression in query
* Support order by timeseries in last query
* Support hot configuration of data_dirs

The full release note is available at:
https://raw.githubusercontent.com/apache/iotdb/master/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: [VOTE] Apache IoTDB 0.13.4 RC1 release

[Haonan Hou]

Hi,

+1 (binding)

The source release:
apache headers [ok]
signatures and hashes [ok]
LICENSE and NOTICE [ok]
no jar files [ok]
could compile from source: ./mvnw.sh clean install -DskipTests [ok]

The binary distribution:
version number in CLI [ok]
signatures and hashes [ok]
start in mac, jdk11 [ok]
statements executed successfully:  [ok]

create database root.turbine;
CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
insert into root.turbine.d1(timestamp,s0) values(1,1);
insert into root.turbine.d1(timestamp,s0) values(2,2);
insert into root.turbine.d1(timestamp,s0) values(3,3);
select ** from root;

Thanks,
—
Haonan Hou

> On Feb 9, 2023, at 5:09 PM, Yuan Tian  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> The source release:
> apache headers [ok]
> signatures and hashes [ok]
> LICENSE and NOTICE [ok]
> no jar files [ok]
> could compile from source: ./mvnw.sh clean install -DskipTests [ok]
> 
> The binary distribution:
> version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk8 [ok]
> statements executed successfully:  [ok]
> 
> SET STORAGE GROUP TO root.turbine;
> CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
> insert into root.turbine.d1(timestamp,s0) values(1,1);
> insert into root.turbine.d1(timestamp,s0) values(2,2);
> insert into root.turbine.d1(timestamp,s0) values(3,3);
> select ** from root;
> 
> Best.
> —
> Yuan Tian

Re: [VOTE] Apache IoTDB 1.0.1 RC1 release

[Haonan Hou]

Hi,

+1 (binding)

The source release:
LICENSE and NOTICE [ok]
signatures and hashes [ok]
All files have ASF header [ok]
could compile from source: ./mvnw clean install [ok]

The binary distribution:
LICENSE and NOTICE [ok]
signatures and hashes [ok]
Could run with the following statements [ok]

CREATE DATABASE root.turbine;
CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
insert into root.turbine.d1(timestamp,s0) values(1,1);
insert into root.turbine.d1(timestamp,s0) values(2,2);
insert into root.turbine.d1(timestamp,s0) values(3,3);
select * from root.**;

Thanks,
Haonan Hou

> On Feb 20, 2023, at 10:44 PM, Jialin Qiao  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> The source release:
> LICENSE and NOTICE [ok]
> signatures and hashes [ok]
> All files have ASF header [ok]
> could compile from source: ./mvnw clean install [ok]
> 
> The binary distribution:
> LICENSE and NOTICE [ok]
> signatures and hashes [ok]
> Could run with the following statements [ok]
> 
> CREATE DATABASE root.turbine;
> CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
> insert into root.turbine.d1(timestamp,s0) values(1,1);
> insert into root.turbine.d1(timestamp,s0) values(2,2);
> insert into root.turbine.d1(timestamp,s0) values(3,3);
> select * from root.**;
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> Gaofei Cao  于2023年2月17日周五 19:26写道：
>> 
>> Hi all,
>> 
>> Apache IoTDB 1.0.1 has been staged under [2] and it’s time to vote
>> on accepting it for release.  All Maven artifacts are available under [1].
>> Voting will be open for 72hr.
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> are required to pass.
>> 
>> Release tag: v1.0.1
>> Hash for the release tag: ff6de906748d9ddc1a3b40a768c3de69fecc6733
>> 
>> Before voting +1, PMC members are required to download
>> the signed source code package, compile it as provided, and test
>> the resulting executable on their own platform, along with also
>> verifying that the package meets the requirements of the ASF policy
>> on releases. [3]
>> 
>> You can achieve the above by following [4].
>> 
>> [ ]  +1 accept (indicate what you validated - e.g. performed the
>> non-RM items in [4])
>> [ ]  -1 reject (explanation required)
>> 
>> 
>> [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1097
>> [2] https://dist.apache.org/repos/dist/dev/iotdb/1.0.1/rc1
>> [3] https://www.apache.org/dev/release.html#approving-a-release
>> [4] 
>> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>> [5] https://dist.apache.org/repos/dist/dev/iotdb/1.0.1/rc1/RELEASE_NOTES.md
>> [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
>> 
>> Best,
>> 
>> Gaofei Cao

Re: Remove UserGuide before 0.13 from website

[Haonan Hou]

+1

Haonan Hou

> On Feb 23, 2023, at 6:30 PM, Jialin Qiao  wrote:
> 
> Hi,
> 
> There are 8 versions UserGuide on our website[1], the old versions are
> hardly used anymore.
> 
> I prefer to remove the history versions before 0.13 (not include).
> 
> [1] https://iotdb.apache.org/
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC

Re: IoTDB quarterly Report (Q1)

[Haonan Hou]

Hi,

Another little correction is that William Song is not an IoTDB committer yet. 
He is only a committer of Ratis community right now.

Best,
Haonan

> On Mar 13, 2023, at 3:16 PM, Pengcheng Zheng  wrote:
> 
> Hi Xiangdong,
> 
> A little correction to the interactions with other ASF communities:
> 
> -An joint online meetup for European (actually for all) developers was
> hosted by IoTDB on March 2nd with SeaTunnel rather than DolphinScheduler.
> 
> 
> Best regards,
> Pengcheng
> 
> 
> 
> Xiangdong Huang  schrieb am Mo. 13. März 2023 um 07:19:
> 
>> Hi all,
>> 
>> The following is the draft of IoTDB report.
>> Please have a look and let me know if there is something missing.
>> 
>> I will submit the report tomorrow (Sorry for less than 3 days).
>> 
>> ## 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:
>> no
>> 
>> ## Membership Data:
>> Apache IoTDB was founded 2020-09-16 (2 years ago)
>> There are currently 56 committers and 27 PMC members in this project.
>> The Committer-to-PMC ratio is roughly 7:4.
>> 
>> Community changes, past quarter:
>> - No new PMC members. Last addition was Chao Wang on 2022-12-12.
>> - Qingxin Feng was added as committer on 2022-12-15
>> - Haiming Zhu was added as committer on 2022-12-29
>> - Junqing Wang was added as committer on 2022-12-15
>> - Hongyin Zhang was added as committer on 2022-12-15
>> - Yongzao Dan was added as committer on 2023-01-04
>> 
>> ## Project Activity:
>> IOTDB-0.13.4 was released on 2023-02-23.
>> IOTDB-1.0.1 was released on 2023-02-22.
>> IOTDB-1.0.0 was released on 2022-12-03.
>> 
>> After releasing v1.0.0,
>> The development of IoTDB (v1.x) is in progress.
>> The community devotes itself to fixing bugs, introducing new features,
>> and keeping the new version more stable.
>> DBA tools like one-click deployment tool are also in development.
>> 
>> One thing that the project and community should consider is how to
>> solve the incompatibility between v0.x and v1.x.
>> 
>> Some security reports are still opened, which should be taken care by PMC.
>> 
>> ## Community Health:
>> The community keeps growing (more stargazers, contributors, etc.).
>> 
>> And, the interaction amng ASF communities grows:
>> - one IoTDB committer is nominated to Ratis committer and acts as
>> release manager of Ratis.
>> - An online meetup for European developers is hosted by IoTDB joint
>> DolphinSchedule on March 2nd.
>> 
>> Mailing list traffic decreases, which the PMC should take care.
>> 
> 

[VOTE] Apache IoTDB 1.1.0 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.1.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.1.0
Hash for the release tag: 12e3f998667c72586139e023fe4521cb4db7c013

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1114
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.1.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.1.0/rc1/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.1.0 RC1 release

[Haonan Hou]

Ok, let me do rc2 releasing later.

Best,
Haonan 

> On Mar 27, 2023, at 10:30 AM, 张金瑞 <329920...@qq.com.INVALID> wrote:
> 
> -1 （binding）
> 
> 
> 
> 
> 
> 
> Hi all,
> 
> 
> I found that the REST API defined in 0.13 is not compatible with 1.1.0, which 
> may lead unexpected error from user side. Let's fix them in this 
> release. 
> 
> 
> Thanks,
> Jinrui
> 
> 
> Original
> 
> 
> 
> From:"Yuan Tian"< jackietie...@gmail.com >;
> 
> Date:2023/3/26 12:28
> 
> To:"dev"< dev@iotdb.apache.org >;
> 
> Subject:Re: [VOTE] Apache IoTDB 1.1.0 RC1 release
> 
> 
> Hi,
> 
> +1 (binding)
> 
> The source release:
> apache headers [ok]
> signatures and hashes [ok]
> LICENSE and NOTICE [ok]
> no jar files [ok]
> could compile from source: ./mvnw.sh clean install [ok]
> 
> The binary distribution:
> version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk-17 [ok]
> statements executed successfully:  [ok]
> 
> 
> insert into root.db.d1(time,s0) values(1,1);
> insert into root.db.d1(time,s0) values(2,2);
> insert into root.db.d1(time,s0) values(3,3);
> select * from root.db.**;
> select count(*) from root.db.** group by level=1;
> 
> Best,
> --
> Yuan Tian
> 
> On Sat, Mar 25, 2023 at 1:20 PM Haonan Hou  wrote:
> >
> > Hi all,
> >
> > Apache IoTDB 1.1.0 has been staged under [2] and it’s time to vote
> > on accepting it for release.  All Maven artifacts are available under 
> [1].
> > Voting will be open for 72hr.
> > A minimum of 3 binding +1 votes and more binding +1 than binding -1
> > are required to pass.
> >
> > Release tag: v1.1.0
> > Hash for the release tag: 12e3f998667c72586139e023fe4521cb4db7c013
> >
> > Before voting +1, PMC members are required to download
> > the signed source code package, compile it as provided, and test
> > the resulting executable on their own platform, along with also
> > verifying that the package meets the requirements of the ASF policy
> > on releases. [3]
> >
> > You can achieve the above by following [4].
> >
> > [ ]  +1 accept (indicate what you validated - e.g. performed the
> > non-RM items in [4])
> > [ ]  -1 reject (explanation required)
> >
> >
> > [1] 
> https://repository.apache.org/content/repositories/orgapacheiotdb-1114
> > [2] https://dist.apache.org/repos/dist/dev/iotdb/1.1.0/rc1
> > [3] https://www.apache.org/dev/release.html#approving-a-release
> > [4] 
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> > [5] 
> https://dist.apache.org/repos/dist/dev/iotdb/1.1.0/rc1/RELEASE_NOTES.md
> > [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> >
> > Best,
> >
> > Haonan Hou

[VOTE] Apache IoTDB 1.1.0 RC2 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.1.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.1.0
Hash for the release tag: 807ec8b9e8006113d941ca7acd2c0a2f28829428

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1115
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.1.0/rc2
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.1.0/rc2/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

[RESULT][VOTE] Release Apache IoTDB 1.1.0

[Haonan Hou]

Hi all,

The release is approved by accepting 4 +1 votes:

4 from PMCs,
Jialin Qiao,
Yuan Tian,
Jinrui Zhang,
Gaofei Cao,



Vote threads: 

https://lists.apache.org/thread/n6sb2qv4tt80w36tmqnknjcxk21d1zlj
https://lists.apache.org/thread/s77px46tdp393vjpthrtlc3nkg3f1z1h

Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.1.0 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.0.0.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.1.0 is the latest version of the v1 series. Feel free to upgrade 
from 1.0.1 or 1.0.0.

## New Features

* [IOTDB-4572] support order by time in align by device
* [IOTDB-4816] Support Show Queries command
* [IOTDB-4817] Support kill query command
* [IOTDB-5077] Support new command formats in  SHOW REGIONS
* [IOTDB-5108] Support region migration
* [IOTDB-5202] Support show regions with specific database
* [IOTDB-5282] Add SQL show variables, which can display the current cluster 
variables
* [IOTDB-5341] Support GROUP BY VARIATION in aggregation query
* [IOTDB-5372] Support data type cast in SELECT INTO
* [IOTDB-5382] Support DIFF as built-in scalar function in IoTDB
* [IOTDB-5393] Show Region creation time when execute show regions
* [IOTDB-5456] Implement COUNT_IF built-in aggregation function
* [IOTDB-5515] Support GROUP BY CONDITION in aggregation query
* [IOTDB-] Enable modify dn_rpc_port and dn_rpc_address in 
datanode-engine.properties
* Support docker deployment
* Rename SeriesSlotId to SeriesSlotNum in show regions

## Improvements

* [IOTDB-4497] Improve NodeStatus definition
* [IOTDB-5066] Upgraded the GetSlots SQLs
* [IOTDB-5161] Add output type check for WHERE & HAVING clause and refuse 
expressions whose return type are not boolean exist in WHERE & HAVING clause
* [IOTDB-5185] Fixed that old snapshot is not deleted in IoTConsensus
* [IOTDB-5287] Added status “Discouraged” to RegionGroup
* [IOTDB-5449] Wait for query resource while the query queue is full instead of 
throwing exception directly
* change STARTUP_RETRY_INTERVAL_IN_MS from 30s to 3s

The full release note is available at:
https://raw.githubusercontent.com/apache/iotdb/master/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: [VOTE] New Repo: iotdb-client-csharp

[Haonan Hou]

+1

Best,
Haonan Hou

> On May 20, 2023, at 8:18 PM, 冯 庆新  wrote:
> 
> +1
> 
> 发件人: Houliang Qi<mailto:neuyi...@163.com>
> 发送时间: 2023年5月20日 19:20
> 收件人: dev@iotdb.apache.org<mailto:dev@iotdb.apache.org>
> 主题: Re:[VOTE] New Repo: iotdb-client-csharp
> 
> +1
> 
> 
> And once the new repositories is created, perhaps it's best to contact the 
> author(github id: eedalong) and see if they are willing to contribute code to 
> iotdb-client-csharp
> 
> 
> 
> 
> 
> Thanks,
> ---
> Houliang Qi
> BONC, Ltd
> 
> 
>  Replied Message 
> | From | gitda...@163.com |
> | Date | 05/20/2023 15:22 |
> | To |  |
> | Subject | Re:[VOTE] New Repo: iotdb-client-csharp |
> +1
> At 2023-05-20 14:57:56, "Jialin Qiao"  wrote:
> Hi,
> 
> Currently, there are two Repositories of IoTDB Csharp client.
> 
> eedalong/Apache-IoTDB-Client-CSharp
> eedalong/Apache-IoTDB-Client-CSharp-UseCase
> 
> I prefer to call for a vote for creating a new repo
> iotdb-client-csharp for the csharp client.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> The vote is open for the next 72 hours and passes if at least three +1
> votes and more +1 votes than -1 votes.
> 
> Best,
> ―
> Jialin Qiao
> Apache IoTDB PMC
> 

[VOTE] Apache IoTDB 1.1.1 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.1.1 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.1.1
Hash for the release tag: d123b8e5ce8b23144107f41d1e1b115314d47ee0

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1116
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.1.1/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://dist.apache.org/repos/dist/dev/iotdb/1.1.1/rc1/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.1.1 RC1 release

[Haonan Hou]

Hi,

+1 (binding)

The source release:
apache headers [ok]
signatures and hashes [ok]
LICENSE and NOTICE [ok]
no jar files [ok]

The binary distribution:
version number in CLI [ok]
signatures and hashes [ok]
start in mac, jdk8 [ok]
statements executed successfully:  [ok]

SET STORAGE GROUP TO root.sg <http://root.sg/>;
CREATE TIMESERIES root.sg.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
insert into root.sg.d1(timestamp,s0) values(1,1);
insert into root.sg.d1(timestamp,s0) values(2,2);
insert into root.sg.d1(timestamp,s0) values(3,3);
select ** from root;

Thanks,
Haonan Hou

> On Jun 12, 2023, at 5:38 PM, 张金瑞 <329920...@qq.com.INVALID> wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> The source release:
> apache headers [ok]
> signatures and hashes [ok]
> LICENSE and NOTICE [ok]
> no jar files [ok]
> 
> The binary distribution:
> version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk8 [ok]
> statements executed successfully:  [ok]
> 
> SET STORAGE GROUP TO root.sg;
> CREATE TIMESERIES root.sg.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
> insert into root.sg.d1(timestamp,s0) values(1,1);
> insert into root.sg.d1(timestamp,s0) values(2,2);
> insert into root.sg.d1(timestamp,s0) values(3,3);
> select ** from root;
> 
> Thanks,
> Jinrui Zhang
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 原始邮件
> 
> 
> 
> 发件人："Jialin Qiao"< qiaojia...@apache.org >;
> 
> 发件时间：2023/6/12 0:38
> 
> 收件人："dev"< dev@iotdb.apache.org >;
> 
> 主题：Re: [VOTE] Apache IoTDB 1.1.1 RC1 release
> 
> 
> Hi,
> 
> +1 (binding)
> 
> The source release:
> apache headers [ok]
> signatures and hashes [ok]
> LICENSE and NOTICE [ok]
> no jar files [ok]
> 
> The binary distribution:
> version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk8 [ok]
> statements executed successfully:  [ok]
> 
> SET STORAGE GROUP TO root.turbine;
> CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
> insert into root.turbine.d1(timestamp,s0) values(1,1);
> insert into root.turbine.d1(timestamp,s0) values(2,2);
> insert into root.turbine.d1(timestamp,s0) values(3,3);
> select ** from root;
> 
> Thanks,
> —
> Jialin Qiao
> 
> 
> On 2023/06/10 17:44:43 Haonan Hou wrote:
> > Hi all,
> > 
> > Apache IoTDB 1.1.1 has been staged under [2] and it’s time to vote
> > on accepting it for release.  All Maven artifacts are available under 
> [1].
> > Voting will be open for 72hr.
> > A minimum of 3 binding +1 votes and more binding +1 than binding -1
> > are required to pass.
> > 
> > Release tag: v1.1.1
> > Hash for the release tag: d123b8e5ce8b23144107f41d1e1b115314d47ee0
> > 
> > Before voting +1, PMC members are required to download
> > the signed source code package, compile it as provided, and test
> > the resulting executable on their own platform, along with also
> > verifying that the package meets the requirements of the ASF policy
> > on releases. [3]
> > 
> > You can achieve the above by following [4].
> > 
> > [ ]  +1 accept (indicate what you validated - e.g. performed the
> > non-RM items in [4])
> > [ ]  -1 reject (explanation required)
> > 
> > 
> > [1] 
> https://repository.apache.org/content/repositories/orgapacheiotdb-1116
> > [2] https://dist.apache.org/repos/dist/dev/iotdb/1.1.1/rc1
> > [3] https://www.apache.org/dev/release.html#approving-a-release
> > [4] 
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> > [5] 
> https://dist.apache.org/repos/dist/dev/iotdb/1.1.1/rc1/RELEASE_NOTES.md
> > [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> > 
> > Best,
> > 
> > Haonan Hou
> >

[RESULT][VOTE] Release Apache IoTDB 1.1.1

[Haonan Hou]

Hi all,

The release is approved by accepting 3 +1 votes:

3 from PMCs,
Jialin Qiao,
Jinrui Zhang,
Haonan Hou.



Vote threads: 

https://lists.apache.org/thread/kktpxh1mg8733lw3rjwjch53ntlh8vjy
https://lists.apache.org/thread/xm2l6pp8tvyw0f9dsnx1mydm026p09zf

Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.1.1 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.1.1.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.1.1 is the latest version of the v1 series. Feel free to upgrade 
from 1.1.0 or earlier version.

## New Feature

* [IOTDB-2569] ZSTD compression

## Improvement/Bugfix

* [IOTDB-5781] Change the default strategy to SequenceStrategy
* [IOTDB-5780] Let users know a node was successfully removed and data is 
recovered
* [IOTDB-5735] The result of adding the distinct function to the align by 
device is incorrect
* [IOTDB-5777] When writing data using non-root users, the permission 
authentication module takes too long
* [IOTDB-5835] Fix wal accumulation caused by datanode restart
* [IOTDB-5828] Optimize the implementation of some metric items in the metric 
module to prevent Prometheus pull timeouts
* [IOTDB-5813] ConfigNode restart error due to installSnapshot failed
* [IOTDB-5657] Limit does not take effect in last query
* [IOTDB-5717] Incorrect result when querying with limit push-downing & order 
by time desc
* [IOTDB-5722] Wrong default execution branch in PlanVisitor
* [IOTDB-5784] Incorrect result when querying with offset push-down and time 
filter
* [IOTDB-5815] NPE when using UDF to query
* [IOTDB-5829] Query with limit clause will cause other concurrent query break 
down
* [IOTDB-5824] show devices with * cannot display satisfied devices
* [IOTDB-5831] Drop database won't delete totally files in disk
* [IOTDB-5818] Cross_space compaction of Aligned timeseries is stucked
* [IOTDB-5859] Compaction error when using Version as first sort dimension
* [IOTDB-5869] Fix load overlap sequence TsFile

The full release note is available at:
https://dlcdn.apache.org/iotdb/1.1.1/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: [discuss] move jenkins build message to a new mailing list

[Haonan Hou]

+1 for option 1.

Best,
Haonan Hou

> On Jun 29, 2023, at 11:44 PM, Xiangdong Huang  wrote:
> 
> Hi all,
> 
> How do you think about move jenkins's notification
> "build-failure"/"build-stable" to a new mailing list?
> 
> Now, it is sent to dev@, and some people may think it is annoying..
> 
> So, how do you think about it?
> 
> option 1: move to an existed mailing list: notifications@ (which is
> for jira issues now)
> option 2: create a new mailing list.
> option 3: keep current status
> 
> Best,
> ---
> Xiangdong Huang

Re: New Repo: iotdb-docs

[Haonan Hou]

+1

Haonan Hou

> On Jul 7, 2023, at 11:58 AM, Jialin Qiao  wrote:
> 
> Hi,
> 
> To manage our different versions of doc uniformly and clean the folder
> of code repo, I'd like to create a new repo: iotdb-docs.
> 
> Then, we could put all versions(0.13, 1.0, 1.1, 1.2) of docs in the
> main branch of iotdb-docs, along with the sidebar. It will be easier
> to update the docs.
> 
> What do you think?
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC

[VOTE] Apache IoTDB 1.2.0 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.2.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.2.0
Hash for the release tag: d0dfef047c912160a925061fc27284129bbcea78

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1118
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.2.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/rc/1.2.0/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.2.0 RC1 release

[Haonan Hou]

Ok, that is an issue… Let me do the RC2.

Haonan Hou

> On Jul 10, 2023, at 3:44 PM, Yuan Tian  wrote:
> 
> Hi,
> 
> -1(binding).
> 
> I try to upgrade from V1.1.1  to V1.2.0, the cluster won't start up
> successfully, there are  error logs in ConfigNode like the following:
> 
> ```
> 2023-07-07 23:44:56,702 [0@group--LeaderElection15] INFO
> o.a.r.s.i.LeaderElection:255 - 0@group--LeaderElection15:
> BufferUnderflowException is safely ignored since this is already
> CLOSING
> java.nio.BufferUnderflowException: null
> at java.base/java.nio.Buffer.nextGetIndex(Buffer.java:651)
> at java.base/java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:402)
> at 
> org.apache.iotdb.tsfile.utils.ReadWriteIOUtils.readInt(ReadWriteIOUtils.java:574)
> at 
> org.apache.iotdb.tsfile.utils.ReadWriteIOUtils.readIntegerSet(ReadWriteIOUtils.java:907)
> at 
> org.apache.iotdb.confignode.procedure.impl.sync.StartPipeProcedure.deserialize(StartPipeProcedure.java:84)
> at 
> org.apache.iotdb.confignode.procedure.store.ProcedureFactory.create(ProcedureFactory.java:172)
> at 
> org.apache.iotdb.confignode.procedure.store.ProcedureWAL.load(ProcedureWAL.java:87)
> at 
> org.apache.iotdb.confignode.persistence.ProcedureInfo.lambda$load$3(ProcedureInfo.java:67)
> at 
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base/java.util.stream.SortedOps$RefSortingSink.end(SortedOps.java:395)
> at java.base/java.util.stream.Sink$ChainedReference.end(Sink.java:258)
> at 
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
> at 
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at 
> java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at 
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at 
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at 
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497)
> at 
> org.apache.iotdb.confignode.persistence.ProcedureInfo.load(ProcedureInfo.java:60)
> at 
> org.apache.iotdb.confignode.procedure.store.ConfigProcedureStore.load(ConfigProcedureStore.java:73)
> at 
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.recover(ProcedureExecutor.java:121)
> at 
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.init(ProcedureExecutor.java:110)
> at 
> org.apache.iotdb.confignode.manager.ProcedureManager.shiftExecutor(ProcedureManager.java:147)
> at 
> org.apache.iotdb.confignode.consensus.statemachine.ConfigRegionStateMachine.notifyLeaderChanged(ConfigRegionStateMachine.java:211)
> at 
> org.apache.iotdb.consensus.ratis.ApplicationStateMachineProxy.notifyLeaderChanged(ApplicationStateMachineProxy.java:297)
> at org.apache.ratis.server.impl.ServerState.setLeader(ServerState.java:315)
> at org.apache.ratis.server.impl.ServerState.becomeLeader(ServerState.java:337)
> at 
> org.apache.ratis.server.impl.RaftServerImpl.changeToLeader(RaftServerImpl.java:566)
> at org.apache.ratis.server.impl.LeaderElection.run(LeaderElection.java:248)
> at java.base/java.lang.Thread.run(Thread.java:829)
> ```
> 
> BTW, I used old pipe feature in v1.1.1 which has been redefined in
> V1.2.0. I think there may exist incompatibility problems.
> 
> Best,
> --
> Yuan Tian
> 
> On Mon, Jul 10, 2023 at 3:12 PM Haonan Hou  wrote:
>> 
>> Hi all,
>> 
>> Apache IoTDB 1.2.0 has been staged under [2] and it’s time to vote
>> on accepting it for release.  All Maven artifacts are available under [1].
>> Voting will be open for 72hr.
>> A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> are required to pass.
>> 
>> Release tag: v1.2.0
>> Hash for the release tag: d0dfef047c912160a925061fc27284129bbcea78
>> 
>> Before voting +1, PMC members are required to download
>> the signed source code package, compile it as provided, and test
>> the resulting executable on their own platform, along with also
>> verifying that the package meets the requirements of the ASF policy
>> on releases. [3]
>> 
>> You can achieve the above by following [4].
>> 
>> [ ]  +1 accept (indicate what you validated - e.g. performed the
>> non-RM items in [4])
>> [ ]  -1 reject (explanation required)
>> 
>> 
>> [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1118
>> [2] https://dist.apache.org/repos/dist/dev/iotdb/1.2.0/rc1
>> [3] https://www.apache.org/dev/release.html#approving-a-release
>> [4] 
>> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>> [5] https://github.com/apache/iotdb/blob/rc/1.2.0/RELEASE_NOTES.md
>> [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
>> 
>> Best,
>> 
>> Haonan Hou

Re: [DISCUSS] Setup Sonarcloud for IoTDB?

[Haonan Hou]

Hi,

Currently, sonar is only checking bugs and code smells for the workflow speed 
reason. The test coverage
reports can only be found in coveralls[1]. 

Best,
Haonan Hou


[1] https://coveralls.io/github/apache/iotdb


> On Jul 15, 2023, at 1:51 PM, Xiangdong Huang  wrote:
> 
> +1 for renaming.
> 
> BTW, seems IoTDB's sonar setting has some errors that test  code
> coverage can not be catched.
> 
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
> 黄向东
> 清华大学 软件学院
> 
> Yuan Tian  于2023年7月15日周六 09:50写道：
>> 
>> We would like to  see that for sure.
>> 
>> 
>> Best,
>> --
>> Yuan Tian
>> 
>> On Fri, Jul 14, 2023 at 10:13 PM Christofer Dutz
>>  wrote:
>>> 
>>> We have to file a Jira ticket for Infra … but wanted to know, if it would 
>>> be ok for you folks for me to do that.
>>> 
>>> Chris
>>> 
>>> Von: Yuan Tian 
>>> Datum: Freitag, 14. Juli 2023 um 15:40
>>> An: dev@iotdb.apache.org 
>>> Betreff: Re: [DISCUSS] Setup Sonarcloud for IoTDB?
>>> Aha, that's right. Do you know how to change that name? I didn't find
>>> where to change that name before.
>>> 
>>> Best,
>>> 
>>> Yuan Tian
>>> 
>>> On Fri, Jul 14, 2023 at 9:31 PM Christofer Dutz
>>>  wrote:
>>>> 
>>>> Hehe … ok … so because of the “incubator” in there, I didn’t find it ;-)
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>> Von: Jialin Qiao 
>>>> Datum: Freitag, 14. Juli 2023 um 15:29
>>>> An: dev@iotdb.apache.org 
>>>> Betreff: Re: [DISCUSS] Setup Sonarcloud for IoTDB?
>>>> Hi,
>>>> 
>>>> We have the sonar cloud:
>>>> https://sonarcloud.io/project/overview?id=apache_incubator-iotdb
>>>> But it is only for committers: https://github.com/apache/iotdb/pull/10548
>>>> 
>>>> Thanks,
>>>> —
>>>> Jialin Qiao
>>>> Apache IoTDB PMC
>>>> 
>>>> Christofer Dutz  于2023年7月14日周五 21:24写道：
>>>>> 
>>>>> Hi folks,
>>>>> 
>>>>> I just had a look and noticed that we currently don’t have Sonarcloud 
>>>>> analysis setup.
>>>>> At apache we have free access to using it for open-soucre and I’d like to 
>>>>> suggest to start using it. Some of the things it reports are definitely 
>>>>> going to be false positives, but it also spots a lot of things that could 
>>>>> cause problems before anyone has to file a bug report.
>>>>> 
>>>>> What are your thoughts on this?
>>>>> 
>>>>> Chris
>>>>> 

Re: [DISCUSS] Setup Sonarcloud for IoTDB?

[Haonan Hou]

Yes, I saw the ticket.
https://issues.apache.org/jira/browse/INFRA-24794.

And GitHub Actions updated
https://github.com/apache/iotdb/pull/10567

Best,
Haonan



> On Jul 17, 2023, at 3:54 PM, Christofer Dutz  
> wrote:
> 
> Hi all,
> 
> so infra updated the name oft he Sonarcloud project:
> https://sonarcloud.io/project/overview?id=apache_iotdb
> 
> Chris
> 
> Von: Haonan Hou 
> Datum: Montag, 17. Juli 2023 um 05:23
> An: dev-iotdb 
> Betreff: Re: [DISCUSS] Setup Sonarcloud for IoTDB?
> Hi,
> 
> Currently, sonar is only checking bugs and code smells for the workflow speed 
> reason. The test coverage
> reports can only be found in coveralls[1].
> 
> Best,
> Haonan Hou
> 
> 
> [1] https://coveralls.io/github/apache/iotdb
> 
> 
>> On Jul 15, 2023, at 1:51 PM, Xiangdong Huang  wrote:
>> 
>> +1 for renaming.
>> 
>> BTW, seems IoTDB's sonar setting has some errors that test  code
>> coverage can not be catched.
>> 
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>> 
>> 黄向东
>> 清华大学 软件学院
>> 
>> Yuan Tian  于2023年7月15日周六 09:50写道：
>>> 
>>> We would like to  see that for sure.
>>> 
>>> 
>>> Best,
>>> --
>>> Yuan Tian
>>> 
>>> On Fri, Jul 14, 2023 at 10:13 PM Christofer Dutz
>>>  wrote:
>>>> 
>>>> We have to file a Jira ticket for Infra … but wanted to know, if it would 
>>>> be ok for you folks for me to do that.
>>>> 
>>>> Chris
>>>> 
>>>> Von: Yuan Tian 
>>>> Datum: Freitag, 14. Juli 2023 um 15:40
>>>> An: dev@iotdb.apache.org 
>>>> Betreff: Re: [DISCUSS] Setup Sonarcloud for IoTDB?
>>>> Aha, that's right. Do you know how to change that name? I didn't find
>>>> where to change that name before.
>>>> 
>>>> Best,
>>>> 
>>>> Yuan Tian
>>>> 
>>>> On Fri, Jul 14, 2023 at 9:31 PM Christofer Dutz
>>>>  wrote:
>>>>> 
>>>>> Hehe … ok … so because of the “incubator” in there, I didn’t find it ;-)
>>>>> 
>>>>> Chris
>>>>> 
>>>>> 
>>>>> Von: Jialin Qiao 
>>>>> Datum: Freitag, 14. Juli 2023 um 15:29
>>>>> An: dev@iotdb.apache.org 
>>>>> Betreff: Re: [DISCUSS] Setup Sonarcloud for IoTDB?
>>>>> Hi,
>>>>> 
>>>>> We have the sonar cloud:
>>>>> https://sonarcloud.io/project/overview?id=apache_incubator-iotdb
>>>>> But it is only for committers: https://github.com/apache/iotdb/pull/10548
>>>>> 
>>>>> Thanks,
>>>>> —
>>>>> Jialin Qiao
>>>>> Apache IoTDB PMC
>>>>> 
>>>>> Christofer Dutz  于2023年7月14日周五 21:24写道：
>>>>>> 
>>>>>> Hi folks,
>>>>>> 
>>>>>> I just had a look and noticed that we currently don’t have Sonarcloud 
>>>>>> analysis setup.
>>>>>> At apache we have free access to using it for open-soucre and I’d like 
>>>>>> to suggest to start using it. Some of the things it reports are 
>>>>>> definitely going to be false positives, but it also spots a lot of 
>>>>>> things that could cause problems before anyone has to file a bug report.
>>>>>> 
>>>>>> What are your thoughts on this?
>>>>>> 
>>>>>> Chris
>>>>>> 

[VOTE] Apache IoTDB 1.1.2 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.1.2 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.1.2
Hash for the release tag: 54819a1d0adfaaceeacfb3eae88da5414071dd3d

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ]  -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1119
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.1.2/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/rc/1.1.2/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

[RESULT][VOTE] Release Apache IoTDB 1.1.2

[Haonan Hou]

Hi all,

The release is approved by accepting 4 +1 votes:

4 from PMCs,
Jialin Qiao,
Jinrui Zhang,
Gaofei Cao,
Yuan Tian.


Vote threads: 

https://lists.apache.org/thread/ydftz7hzl2rcc7fkq5bgvfhoo9n9794o

Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.1.2 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.1.2.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.1.2 is the latest version of the v1 series. Feel free to upgrade
from 1.1.1 or earlier version.

## New Feature

* [IOTDB-5919]show variables add a variable timestamp_precision
* Add Python SessionPool

## Improvement/Bugfix

* [IOTDB-5901] Load: load tsfile without data will throw NPE
* [IOTDB-5903] Fix cannot select any inner space compaction task when there is 
only unsequence data
* [IOTDB-5878] Allow ratis-client retry when gRPC IO Unavailable
* [IOTDB-5939] Correct Flusing Task Timeout Detect Thread
* [IOTDB-5905] Fix aligned timeseries data point lost after flushed in some 
scenario
* [IOTDB-5963] Make sure that TsBlock blocked on memory is added in queue 
before the next TsBlock returned by root operator
* [IOTDB-5819] Fix npe when booting net metrics
* [IOTDB-6023] Pipe: Fix load tsfile error while handling empty value chunk
* [IOTDB-5971] Fix potential QUOTE problem in iotdb reporter
* [IOTDB-5993] ConfigNode leader changing causes lacking some DataPartition 
allocation result in the response of getOrCreateDataPartition method
* [IOTDB-5910] Fix compaction scheduler thread pool is not shutdown when 
aborting compaction
* [IOTDB-6056] Pipe: Failed to load tsfile with empty pages (NPE occurs when 
loading)
* [IOTDB-5916]Fix exception when file is deleted during compaction selection
* [IOTDB-5896] Fix the NPE issue when taking snapshot in WAL combined with 
Aligned Binary
* [IOTDB-5929] Enable DataPartition inherit policy
* [IOTDB-5934] Optimize cluster partition policy
* [IOTDB-5926] Remove Useless Rater in Timer
* [IOTDB-6030] Improve efficiency of ConfigNode PartitionInfo takeSnapshot
* [IOTDB-5997] Improve efficiency of ConfigNode PartitionInfo loadSnapshot
* Fix potential deadlock when freeing memory in MemoryPool
* Release resource of FI after all drivers have been closed
* Set default degree of parallelism back to the num of CPU
* Make SequenceStrategy and MaxDiskUsableSpaceFirstStrategy are allowed in 
cluster mode
* Fix npe exception when invalid in metric module
* Fix CQ does not take effect in ns time_precision
* Fix storage engine memory config initialization
* Fix template related schema query
* add default charset setting in start-datanode.bat and print default charset 
when starting
* Fix TsfileResource error after delete device in sequence working memtable
* load TsFile bugs: Not checking whether the tsfile data loaded locally is in 
the same time partition during the loading process & LoadTsFilePieceNode error 
when loading tsfile with empty value chunks
* Fix alias query failure after restarting DataNode
The full release note is available at:
https://dlcdn.apache.org/iotdb/1.1.2/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: Continuing the refactoring of the build: Generated Code

[Haonan Hou]

Hi Chris,

> Also did I see that for some reason we’re copying the python generated code 
> into the mlnode module … what’s that for?

Mlnode is a new module in progress for providing interfaces for machine 
learning. 

> It looks as if the generated go code isn’t used anywhere … shouldn’t we then 
> also remove the go-code generation invocation?

The generated go code is for iotdb-go-client 
https://github.com/apache/iotdb-client-go. Currently, we copy the generated code
to that repo manually to update the thrift interface. We can find another 
better way to do it.

Haonan


> On Aug 15, 2023, at 9:33 PM, Christofer Dutz  
> wrote:
> 
> Hi all,
> 
> So, after I’m now quite happy about the untangled Java part, and while going 
> through the documentation, I noticed some things:
> 
> We’re currently generating the python and go code as part of the build of the 
> protocol modules.
> Then in the client-py, we copy that code around.
> Wouldn’t it be better if we simply generated the code in the client-py module 
> directly?
> 
> Also did I see that for some reason we’re copying the python generated code 
> into the mlnode module … what’s that for?
> 
> It looks as if the generated go code isn’t used anywhere … shouldn’t we then 
> also remove the go-code generation invocation?
> 
> Chris

Re: Deploying the iotdb-tools-thrift artifacts ...

[Haonan Hou]

+1 

Haonan

On 2023/08/16 12:19:44 Christofer Dutz wrote:
> Hi all,
> 
> 
> Today I was made aware that there were issues with the thrift compiler 
> artifacts that I switched to using in my last refactoring.
> 
> When having a look in Nexus I could see that the libraries staged there 
> weren’t the ones I put there as they had a different structure, were no 
> longer containing statically linked thrift executables, didn’t have libraries 
> and includes in them. So someone must have deployed them but must have used 
> an old state of the master branch.
> 
> But we solved the problem, why they keep on disappearing :-/
> 
> When deploying all 5 artifacts, we run a maven build 5 times and deploy 5 
> snapshots of the same artifact. On Saturday a cleanup job removes all but the 
> newest 3 snapshots of each artifact.
> 
> So if we want to keep on using the SNAPSHOT versions, we will have to 
> re-reploy them every Saturday.
> 
> I would however encourage us to do something different:
> 
> Move the “tools” part into the https://github.com/apache/iotdb-bin-resources 
> repo and release the iotdb-tools-thift library (I’d recommend simply using 
> the thrift version instead of the iotdb version as the library actually has 
> absolutely nothing to do with iotdb and is just a compilation of thrift 
> packaged in a way that we can use it.
> Then this problem would be gone forever and we’d only need to re-do it if we 
> switch to a new Thrift version.
> 
> What do you think?
> 
> Chris
> 
> 

Re: Deploying the iotdb-tools-thrift artifacts ...

[Haonan Hou]

I have one more question. If we are going to release the iotdb-tools-thift 
library, do we need to a vote for it?

Haonan 

On 2023/08/16 12:19:44 Christofer Dutz wrote:
> Hi all,
> 
> 
> Today I was made aware that there were issues with the thrift compiler 
> artifacts that I switched to using in my last refactoring.
> 
> When having a look in Nexus I could see that the libraries staged there 
> weren’t the ones I put there as they had a different structure, were no 
> longer containing statically linked thrift executables, didn’t have libraries 
> and includes in them. So someone must have deployed them but must have used 
> an old state of the master branch.
> 
> But we solved the problem, why they keep on disappearing :-/
> 
> When deploying all 5 artifacts, we run a maven build 5 times and deploy 5 
> snapshots of the same artifact. On Saturday a cleanup job removes all but the 
> newest 3 snapshots of each artifact.
> 
> So if we want to keep on using the SNAPSHOT versions, we will have to 
> re-reploy them every Saturday.
> 
> I would however encourage us to do something different:
> 
> Move the “tools” part into the https://github.com/apache/iotdb-bin-resources 
> repo and release the iotdb-tools-thift library (I’d recommend simply using 
> the thrift version instead of the iotdb version as the library actually has 
> absolutely nothing to do with iotdb and is just a compilation of thrift 
> packaged in a way that we can use it.
> Then this problem would be gone forever and we’d only need to re-do it if we 
> switch to a new Thrift version.
> 
> What do you think?
> 
> Chris
> 
> 

Re: Deploying the iotdb-tools-thrift artifacts ...

[Haonan Hou]

Good, looking forward your update about it. :)

Best,
Haonan

On 2023/08/17 07:08:39 Christofer Dutz wrote:
> Yeah we sort of do... But the content of the artifact is going to contain two 
> xml files. But it's going to simplify things a lot.
> 
> Chris
> 
> Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> ________
> From: Haonan Hou 
> Sent: Thursday, August 17, 2023 3:54:43 AM
> To: dev@iotdb.apache.org 
> Subject: Re: Deploying the iotdb-tools-thrift artifacts ...
> 
> I have one more question. If we are going to release the iotdb-tools-thift 
> library, do we need to a vote for it?
> 
> Haonan
> 
> On 2023/08/16 12:19:44 Christofer Dutz wrote:
> > Hi all,
> >
> >
> > Today I was made aware that there were issues with the thrift compiler 
> > artifacts that I switched to using in my last refactoring.
> >
> > When having a look in Nexus I could see that the libraries staged there 
> > weren’t the ones I put there as they had a different structure, were no 
> > longer containing statically linked thrift executables, didn’t have 
> > libraries and includes in them. So someone must have deployed them but must 
> > have used an old state of the master branch.
> >
> > But we solved the problem, why they keep on disappearing :-/
> >
> > When deploying all 5 artifacts, we run a maven build 5 times and deploy 5 
> > snapshots of the same artifact. On Saturday a cleanup job removes all but 
> > the newest 3 snapshots of each artifact.
> >
> > So if we want to keep on using the SNAPSHOT versions, we will have to 
> > re-reploy them every Saturday.
> >
> > I would however encourage us to do something different:
> >
> > Move the “tools” part into the 
> > https://github.com/apache/iotdb-bin-resources repo and release the 
> > iotdb-tools-thift library (I’d recommend simply using the thrift version 
> > instead of the iotdb version as the library actually has absolutely nothing 
> > to do with iotdb and is just a compilation of thrift packaged in a way that 
> > we can use it.
> > Then this problem would be gone forever and we’d only need to re-do it if 
> > we switch to a new Thrift version.
> >
> > What do you think?
> >
> > Chris
> >
> >
> 

Re: AW: Deploying the iotdb-tools-thrift artifacts ...

[Haonan Hou]

+1 for the vote.

Haonan

On 2023/08/17 15:47:17 Christofer Dutz wrote:
> Ok,
> 
> it turns out that the windows artifacts were „Debug” versions … had to 
> re-stage the artifacts:
> https://repository.apache.org/content/repositories/orgapacheiotdb-1129/
> 
> Chris
> 
> 
> Von: Christofer Dutz 
> Datum: Donnerstag, 17. August 2023 um 15:46
> An: dev@iotdb.apache.org 
> Betreff: AW: Deploying the iotdb-tools-thrift artifacts ...
> Giving the artifacts a spin in a PR:
> https://github.com/apache/iotdb/pull/10893
> 
> Chris
> 
> Von: Christofer Dutz 
> Datum: Donnerstag, 17. August 2023 um 15:29
> An: dev@iotdb.apache.org 
> Betreff: AW: Deploying the iotdb-tools-thrift artifacts ...
> Hi all,
> 
> So, I finished copying the iotdb-tools-thrift to the other repo and set it up 
> to work independently from the rest of our build.
> https://github.com/apache/iotdb-bin-resources/tree/main/iotdb-tools-thrift
> 
> This produces the thrift module under a slightly different groupId:
> 
> 
> org.apache.iotdb.tools
> iotdb-tools-thrift
> 0.14.1.0
> 
> 
> The different groupId indicates that it’s not part of the main repo.
> 
> And I was a bit torn about the version number:
> 
>   *   1.3.0-SNAPSHOT (Was sub ideal, as the artifact generally has no 
> relation to IoTDB, but more to Thrift)
>   *   1.14.1 (Also felt sub-ideal, as we couldn’t update the configuration, 
> if we needed to re-deploy without changing the Thrift version)
>   *   1.3.0-SNAPSHOT-1.14.1 (Felt even worse, as it’s so long and we would 
> actually need to re-release everything before every IoTDB version)
>   *   1.14.1.0 (Was what I chose … it shows the relation to Thrift and it 
> allows us to re-deploy updated versions of the binary artifacts)
> 
> Also did I take the library of testing staging of release artifacts.
> https://repository.apache.org/content/repositories/orgapacheiotdb-1128/
> 
> Currently the deployment process still feels a bit rough … I’ve documented 
> it, but I guess I’ll be able to soften the edges over time.
> 
> If you folks agree, I’d be for starting a vote on releasing the RC that I 
> staged in above repo.
> 
> Then we should no longer have any problems with deleted thrift binaries and 
> we should be able to build on all platforms without any complicated setup.
> 
> Chris
> 
> 
> 
> 
> Von: Haonan Hou 
> Datum: Donnerstag, 17. August 2023 um 09:25
> An: dev@iotdb.apache.org 
> Betreff: Re: Deploying the iotdb-tools-thrift artifacts ...
> Good, looking forward your update about it. :)
> 
> Best,
> Haonan
> 
> On 2023/08/17 07:08:39 Christofer Dutz wrote:
> > Yeah we sort of do... But the content of the artifact is going to contain 
> > two xml files. But it's going to simplify things a lot.
> >
> > Chris
> >
> > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> > 
> > From: Haonan Hou 
> > Sent: Thursday, August 17, 2023 3:54:43 AM
> > To: dev@iotdb.apache.org 
> > Subject: Re: Deploying the iotdb-tools-thrift artifacts ...
> >
> > I have one more question. If we are going to release the iotdb-tools-thift 
> > library, do we need to a vote for it?
> >
> > Haonan
> >
> > On 2023/08/16 12:19:44 Christofer Dutz wrote:
> > > Hi all,
> > >
> > >
> > > Today I was made aware that there were issues with the thrift compiler 
> > > artifacts that I switched to using in my last refactoring.
> > >
> > > When having a look in Nexus I could see that the libraries staged there 
> > > weren’t the ones I put there as they had a different structure, were no 
> > > longer containing statically linked thrift executables, didn’t have 
> > > libraries and includes in them. So someone must have deployed them but 
> > > must have used an old state of the master branch.
> > >
> > > But we solved the problem, why they keep on disappearing :-/
> > >
> > > When deploying all 5 artifacts, we run a maven build 5 times and deploy 5 
> > > snapshots of the same artifact. On Saturday a cleanup job removes all but 
> > > the newest 3 snapshots of each artifact.
> > >
> > > So if we want to keep on using the SNAPSHOT versions, we will have to 
> > > re-reploy them every Saturday.
> > >
> > > I would however encourage us to do something different:
> > >
> > > Move the “tools” part into the 
> > > https://github.com/apache/iotdb-bin-resources repo and release the 
> > > iotdb-tools-thift library (I’d recommend simply using the thrift version 
> > > instead of the iotdb version as the library actually has absolutely 
> > > nothing to do with iotdb and is just a compilation of thrift packaged in 
> > > a way that we can use it.
> > > Then this problem would be gone forever and we’d only need to re-do it if 
> > > we switch to a new Thrift version.
> > >
> > > What do you think?
> > >
> > > Chris
> > >
> > >
> >
> 

Re: AW: [VOTE] Release IotDB-Tools: Thrift artifacts

[Haonan Hou]

+1 (binding)

checked each file in the source-zip and all contained all necessary Apache 
headers.
The archive contained the NOTICE and LICENCE files.

tested the mac-arm64 and linux-x86_64 artifacts in my local systems

Haonan


On 2023/08/21 07:08:19 Christofer Dutz wrote:
> +1 (binding)
> 
> I checked each file in the source-zip and all contained all necessary Apache 
> headers.
> The archive contained the NOTICE and LICENCE files.
> 
> I’ve tested all 3 x86_64 in my IoTDB pull request: 
> https://github.com/apache/iotdb/pull/10893
> I’ve tested the aarm64 and x86_64 artifacts in my local systems and VMs
> 
> Chris
> 
> 
> Von: Christofer Dutz 
> Datum: Montag, 21. August 2023 um 09:05
> An: dev@iotdb.apache.org 
> Betreff: [VOTE] Release IotDB-Tools: Thrift artifacts
> Hi all,
> 
> as you all might know, I have worked on streamlining our build for all 
> possible platforms.
> In order to work around us having to re-deploy these artifacts every 
> Saturday, I have moved the artifacts out of the main repo into the 
> iotdb-bin-resources git repo.
> 
> I’ve staged the artifacts at:
> https://repository.apache.org/content/repositories/orgapacheiotdb-1129
> 
> Tag Name: iotdb-tools-thrift-v0.14.1.0
> https://github.com/apache/iotdb-bin-resources/releases/tag/iotdb-tools-thrift-v0.14.1.0
> 
> The source bundle generally consists of a pom.xml and an assembly xml … so it 
> should be quick to review.
> https://repository.apache.org/service/local/repositories/orgapacheiotdb-1129/content/org/apache/iotdb/tools/iotdb-tools-thrift/0.14.1.0/iotdb-tools-thrift-0.14.1.0-source-release.zip
> 
> I’m intentionally not staging it on the release-svn, as nobody should be 
> required to consume this module but us ourselves.
> 
> The vote stays open for 72hours … assuming enough support, I’ll then finish 
> changing the main repo to use these artifacts.
> 
> 
> Chris
> 

Move Jenkins notifications to another list

[Haonan Hou]

Hi,

I think the daily Jenkins build notification is a lot bit noisy. It may be 
better to move it to another list.
Such as notificati...@iotdb.apache.org <mailto:notificati...@iotdb.apache.org>. 

Any idea? 

Best,
Haonan Hou

Re: “Unsupported type VECTOR” Exception when read tsfile use spark

[Haonan Hou]

Hi,

Would you like to post your issue on github? And provide more details about it.

Best,
Haonan

On 2023/08/18 05:47:19 张 wrote:
> I got an exception when I used spark to read tsfile 
> such like this :
> -
> java.lang.UnsupportedOperationException: Unsupported type VECTOR
>   at 
> org.apache.iotdb.spark.tsfile.WideConverter$$anonfun$toSqlField$1.apply(WideConverter.scala:219)
>   at 
> org.apache.iotdb.spark.tsfile.WideConverter$$anonfun$toSqlField$1.apply(WideConverter.scala:211)
> 
> 
> -
> I found it in source code 
> 
> 
> but the tsfile's datatype that I used just include double and text type  in 
> iotdb 。  I didn't know why throw that UnsupportedOperationException. who can 
> help me thanks
> 
> 

Re: Problem building c++ on Windows

[Haonan Hou]

Hi,

The issue fixed by commit 
https://github.com/apache/iotdb/commit/df262ee6c0d6892efd0ff9887f2dc96eec62c9ae 
.

Best,
Haonan 

On 2023/08/17 08:35:16 Christofer Dutz wrote:
> Hi,
> 
> I was just made aware that there seem to be issues building IoTDB with 
> enabled C++ profiles on Windows machines … I’m on it.
> 
> Chris
> 
> 

Simplify the python client package process

[Haonan Hou]

Hi,

I submitted a PR[1] to simplify the python client package process. We can get a 
whl package by running `./release.sh` now.

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

Best,
Haonan Hou 

Re: Move Jenkins notifications to another list

[Haonan Hou]

https://github.com/apache/iotdb/pull/11029
Done.

Thanks,
Haonan

On 2023/09/04 03:13:22 Gaofei Cao wrote:
> strongly +1, it's really disturbing for many [BUILD-UNSTABLE] emails..
> 
> Best,
> Gaofei
> 
> Christofer Dutz  于2023年8月24日周四 15:04写道：
> >
> > Hi,
> >
> > If we have any build emails else than for “master”, I would agree to have 
> > them on other lists.
> >
> > For the ones going to master, the problem is much more the flaky tests.
> > We should put more effort into making sure build failures are indeed errors 
> > that need working on.
> > With a build that randomly fails and people have become used to simply 
> > clicking on “re-run failed tests” a CI sort of looses a big portion of what 
> > it should provide.
> >
> > Chris
> >
> >
> > Von: Haonan Hou 
> > Datum: Donnerstag, 24. August 2023 um 04:28
> > An: dev-iotdb 
> > Betreff: Move Jenkins notifications to another list
> > Hi,
> >
> > I think the daily Jenkins build notification is a lot bit noisy. It may be 
> > better to move it to another list.
> > Such as notificati...@iotdb.apache.org 
> > <mailto:notificati...@iotdb.apache.org>.
> >
> > Any idea?
> >
> > Best,
> > Haonan Hou
> 

[VOTE] Apache IoTDB 1.2.0 RC2 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.2.0 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.2.0
Hash for the release tag: 5c1b68224b9bd77c3aab6e234de532a10c1edcae

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1130
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.2.0/rc2
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/rc/1.2.0/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

[RESULT][VOTE] Release Apache IoTDB 1.2.0

[Haonan Hou]

Hi all,

The release is approved by accepting 4 +1 votes:

4 from PMCs,
Jialin Qiao,
Gaofei Cao,
Christofer Dutz,
Yuan Tian.


Vote threads:

https://lists.apache.org/thread/olodmbs5nh9cg7g8bvxt9vx862w5sy6j

Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.2.0 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.2.0.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.2.0 is the latest version of the v1 series. Feel free to upgrade
from 1.1.2 or earlier version.

## New Feature

* [IOTDB-5567] add SQL for querying seriesslotid and timeslotid
* [IOTDB-5631] Add a built-in aggregation functions named time_duration
* [IOTDB-5636] Add round as built-in scalar function
* [IOTDB-5637] Add substr as built-in scalar function
* [IOTDB-5638] Support case when syntax in IoTDB
* [IOTDB-5643] Add REPLACE as a built-in scalar function
* [IOTDB-5683] Support aggregation function Mode for query
* [IOTDB-5711] Python API should support connecting multiple nodes
* [IOTDB-5752] Python Client supports write redirection
* [IOTDB-5765] Support Order By Expression
* [IOTDB-5771] add SPRINTZ and RLBE encodor and LZMA2 compressor
* [IOTDB-5924] Add SessionPool deletion API
* [IOTDB-5950] Support Dynamic Schema Template
* [IOTDB-5951] Support show timeseries/device with specific string contained in 
path 
* [IOTDB-5955] Support create timeseries using schema template in Session API

## Improvements

* [IOTDB-5630] Make function cast a built-in function
* [IOTDB-5689] Close Isink when ISourceHandle is closed
* [IOTDB-5715] Improve the performance of query order by time desc
* [IOTDB-5763] Optimize the memory estimate for INTO operations
* [IOTDB-5887] Optimize the construction performance of PathPatternTree without 
wildcards
* [IOTDB-5888] TTL logs didn' t consider timestamp precision
* [IOTDB-5896] Failed to execute delete statement
* [IOTDB-5908] Add more query metrics
* [IOTDB-5911] print-iotdb-data-dir tool cannot work
* [IOTDB-5914] Remove redundant debug log in Session
* [IOTDB-5919] show variables add a variable timestamp_precision 
* [IOTDB-5926] Optimize metric implementation
* [IOTDB-5929] Enable DataPartition inherit policy
* [IOTDB-5943] Avoid rpc invoking for SimpleQueryTerminator when endpoint is 
local address
* [IOTDB-5944] Follower doesn' t need to update last cache when using 
IoT_consensus
* [IOTDB-5945] Add a cache to avoid initialize duplicated device id object in 
write process
* [IOTDB-5946] Optimize the implement of tablet in Go client
* [IOTDB-5949] Support show timeseries with datatype filter
* [IOTDB-5952] Support FIFO strategy in DataNodeSchemaCache
* [IOTDB-6022] The WAL piles up when multi-replica iotconsensus is written at 
high concurrency


The full release note is available at:
https://dlcdn.apache.org/iotdb/1.2.0/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: [DISCUSS] Switch to Java 11 for building, but staying at Java 8 for compiling?

[Haonan Hou]

Hi,

I have a question. If we do that and hope to run UT/IT with jdk 8 by mvn 
commands, how to separate the compile and test with the different jdk versions?

Best,
Haonan

On 2023/09/12 13:27:19 Christofer Dutz wrote:
> Hi all,
> 
> while updating some of our plugins, I ran into the problem, that some newer 
> versions of the plugins or dependencies only work with Java 11.
> 
> In PLC4X we had similar problems. So, we decided to switch to at least Java 
> 11 for building, but still ensure the output is compatible with Java 8.
> 
> This way we can benefit from plugin updates and still not loose compatibility.
> 
> There are even plugins available to validate API compatibility with Java 8 
> SDKs.
> 
> Chris
> 
> 

[VOTE] Apache IoTDB 1.2.1 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.2.1 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.2.1
Hash for the release tag: aa24cb65b839d12ec83dcdbd4e94155f0891e18d

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1131
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.2.1/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/rc/1.2.1/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Re: AW: [DISCUSS] Updating to a newer Thrift version?

[Haonan Hou]

It seems that Thrift 0.19.0 is released and supports Java 8 again. ;-)
https://github.com/apache/thrift/blob/master/CHANGES.md

Best,
Haonan

On 2023/08/04 10:01:39 Christofer Dutz wrote:
> Ok …
> 
> So, it turns out that the Thrift folks intentionally updated to Java 11 but 
> took that back and the next release should be based on Java 8 again.
> So hopefully that will come soon and then we could have a look about 
> compatibility of the generated code. I guess if the wire-protocol didn’t 
> change there should generally be no reason for it to not be compatible, and 
> if they don’t release a major version, usually this compatibility should stay 
> intact (if they sort of follow SemVer)
> 
> I guess the best path of action would be to do nothing right now … as an 
> alternative, we could of course turn on the Java compilation when building 
> thrift and to bundle the jar built by that in the assembly.
> If we then replace the thrift-lib dependency with a “system” scope 
> dependency, we could already do that now. But admittedly I would not be in 
> favor of doing that. I would recommend for us to wait for the next official 
> release.
> 
> Chris
> 
> Von: Christofer Dutz 
> Datum: Dienstag, 1. August 2023 um 08:29
> An: dev@iotdb.apache.org 
> Betreff: Re: [DISCUSS] Updating to a newer Thrift version?
> I opened a ticket in their jira. Might even prepare a pr... Shouldn't be too 
> difficult.
> 
> Chris
> 
> Gesendet von Outlook für Android
> 
> From: 谭新宇 <1025599...@qq.com.INVALID>
> Sent: Monday, July 31, 2023 1:57:28 PM
> To: dev@iotdb.apache.org 
> Subject: Re: [DISCUSS] Updating to a newer Thrift version?
> 
> Hi, Chris
> 
> In the latest version of thrift, there are some improvements we'd like to 
> make, For example, https://issues.apache.org/jira/browse/THRIFT-5502 will 
> down-cycled  "connection reset"  warn logs.
> 
> +1 for upgrading thrift.
> 
> 
> Thanks
> 
> Xinyu Tan
> 
> > 2023年7月31日 19:50，Christofer Dutz  写道：
> >
> > Hi all,
> >
> > While working on the cleanup of the build, I noticed we’re working with 
> > Thrift in version 0.14.1 however the latest version is 0.18.1
> >
> > Is there a reason we’re sticking to a two-year older version than the 
> > newest?
> >
> > If not: with the pom-cleanup refactoring it should be a thing of minutes to 
> > update this.
> >
> > Chris
> >
> 

[RESULT][VOTE] Release Apache IoTDB 1.2.1

[Haonan Hou]

Hi all,

The release is approved by accepting 3 +1 votes:

3 from PMCs,
Jialin Qiao,
Gaofei Cao,
Yuan Tian.


Vote threads:

https://lists.apache.org/thread/k3mbb69d66y26gzxp4rohbvth58j9v9g

Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.2.1 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.2.1.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.2.1 is the latest version of the v1 series. Feel free to upgrade
from 1.2.0 or earlier version.

## Features & Improvements

- [IOTDB-5557] The metadata query results are inconsistent
- [IOTDB-5997] Improve efficiency of ConfigNode PartitionInfo loadSnapshot
- [IOTDB-6019] Fix concurrent update of last query
- [IOTDB-6036] The mods file is too large, causing Query very slow even OOM 
problem
- [IOTDB-6055] Enable auto restart of the pipes stopped by ConfigNode because 
of critical exception
- [IOTDB-6066] Add ConfigNode timeslot metric
- [IOTDB-6073] Add ClientManager metrics
- [IOTDB-6077] Add force stop
- [IOTDB-6079] Cluster computing resource balance
- [IOTDB-6082] Improve disk space metrics
- [IOTDB-6087] Implement stream interface of Mods read
- [IOTDB-6090] Add memory estimator on inner space compaction
- [IOTDB-6092] Factor mods files into memory estimates for cross-space 
compaction tasks
- [IOTDB-6093] Add multiple validation methods after compaction
- [IOTDB-6106] Fixed the timeout parameter not working in thrift asyncClient
- [IOTDB-6108] AlignedTVList memory calculation is imprecise
- 
## Bugs

- [IOTDB-5855] DataRegion leader Distribution is same as DataRegion Distribution
- [IOTDB-5860] Total Number of file is wrong
- [IOTDB-5996] Incorrect time display of show queries
- [IOTDB-6057] Resolve the compatibility from 1.1.x to 1.2.0
- [IOTDB-6065] Considering LastCacheContainer in the memory estimation of 
SchemaCacheEntry
- [IOTDB-6074] Ignore error message when TagManager createSnapshot
- [IOTDB-6075] Pipe: File resource races when different tsfile load operations 
concurrently modify the same tsfile at receiver
- [IOTDB-6076] Add duplicate checking when upsert alias
- [IOTDB-6078] fix timeChunk default compressType
- [IOTDB-6089] Improve the lock behaviour of the pipe heartbeat
- [IOTDB-6091] Add compression and encoding type check for 
FastCompactionPerformer
- [IOTDB-6094] Load：Fix construct tsFileResource bug
- [IOTDB-6095] Tsfiles in sequence space may be overlap with each other due to 
LastFlushTime bug
- [IOTDB-6096] M4 will output zero while meeting null
- [IOTDB-6097] ipe subscription running with the pattern option may cause OOM
- [IOTDB-6098] Flush error when writing aligned timeseries
- [IOTDB-6100] Pipe: Fix running in hybrid mode will cause wal cannot be 
deleted & some pipe data lost due to wrong ProducerType of Disruptor
- [IOTDB-6105] Load: NPE when analyzing tsfile

The full release note is available at:
https://dlcdn.apache.org/iotdb/1.2.1/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: AW: AW: [DISCUSS] Updating to a newer Thrift version?

[Haonan Hou]

Ok, just pushed a branch using the staged thrift 0.19.0 generator.
https://github.com/apache/iotdb/pull/11183

We need to do more tests on it before the upgrading, such as using the old 
client with Thrift 0.14.1 to connect the data node with 0.19.0. Using the old 
data node to connect the config node with new Thrift... 

Best,
Haonan

On 2023/09/19 08:02:57 Christofer Dutz wrote:
> The repo id of the staged thirft 0.19.0 generator is here:
> https://repository.apache.org/content/repositories/orgapacheiotdb-1132
> 
> So, adding that repository and switching to:
> 0.19.0.0
> 
> 0.19.0
> 
> Should do the trick.
> 
> Chris
> 
> Von: Christofer Dutz 
> Datum: Dienstag, 19. September 2023 um 08:50
> An: dev@iotdb.apache.org 
> Betreff: AW: AW: [DISCUSS] Updating to a newer Thrift version?
> I��m currently preparing the build-tools for 0.19.0.
> As soon as that��s done, we could simply build iotdb with 0.19.0.0 and simply 
> try it out?
> I couldn��t find any info on the binary protocol being changed in the 
> release-notes.
> But I guess simply trying it out should help.
> 
> Chris
> 
> Von: Xiangdong Huang 
> Datum: Dienstag, 19. September 2023 um 01:50
> An: dev@iotdb.apache.org 
> Betreff: Re: AW: [DISCUSS] Updating to a newer Thrift version?
> Hi,
> one more concern, is Thrift v0.19 compatible with Thrift v0.14? (It is
> better to be compatible for all IoTDB v1.x. )
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
>  
> �廪��ѧ ѧԺ
> 
> 
> Haonan Hou  ��2023��9��18һ 18:13д
> 
> > It seems that Thrift 0.19.0 is released and supports Java 8 again. ;-)
> > https://github.com/apache/thrift/blob/master/CHANGES.md
> >
> > Best,
> > Haonan
> >
> > On 2023/08/04 10:01:39 Christofer Dutz wrote:
> > > Ok ��
> > >
> > > So, it turns out that the Thrift folks intentionally updated to Java 11
> > but took that back and the next release should be based on Java 8 again.
> > > So hopefully that will come soon and then we could have a look about
> > compatibility of the generated code. I guess if the wire-protocol didn��t
> > change there should generally be no reason for it to not be compatible, and
> > if they don��t release a major version, usually this compatibility should
> > stay intact (if they sort of follow SemVer)
> > >
> > > I guess the best path of action would be to do nothing right now �� as an
> > alternative, we could of course turn on the Java compilation when building
> > thrift and to bundle the jar built by that in the assembly.
> > > If we then replace the thrift-lib dependency with a ��system�� scope
> > dependency, we could already do that now. But admittedly I would not be in
> > favor of doing that. I would recommend for us to wait for the next official
> > release.
> > >
> > > Chris
> > >
> > > Von: Christofer Dutz 
> > > Datum: Dienstag, 1. August 2023 um 08:29
> > > An: dev@iotdb.apache.org 
> > > Betreff: Re: [DISCUSS] Updating to a newer Thrift version?
> > > I opened a ticket in their jira. Might even prepare a pr... Shouldn't be
> > too difficult.
> > >
> > > Chris
> > >
> > > Gesendet von Outlook f��r Android<https://aka.ms/AAb9ysg>
> > > 
> > > From: ̷ <1025599...@qq.com.INVALID>
> > > Sent: Monday, July 31, 2023 1:57:28 PM
> > > To: dev@iotdb.apache.org 
> > > Subject: Re: [DISCUSS] Updating to a newer Thrift version?
> > >
> > > Hi, Chris
> > >
> > > In the latest version of thrift, there are some improvements we'd like
> > to make, For example, https://issues.apache.org/jira/browse/THRIFT-5502
> > will down-cycled  "connection reset"  warn logs.
> > >
> > > +1 for upgrading thrift.
> > >
> > >
> > > Thanks
> > > �D�D�D�D�D�D�D�D�D�D�D�D
> > > Xinyu Tan
> > >
> > > > 2023��7��31�� 19:50��Christofer Dutz  д
> > > >
> > > > Hi all,
> > > >
> > > > While working on the cleanup of the build, I noticed we��re working
> > with Thrift in version 0.14.1 however the latest version is 0.18.1
> > > >
> > > > Is there a reason we��re sticking to a two-year older version than the
> > newest?
> > > >
> > > > If not: with the pom-cleanup refactoring it should be a thing of
> > minutes to update this.
> > > >
> > > > Chris
> > > >
> > >
> >
> 

[VOTE] Apache IoTDB 1.2.2 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.2.2 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.2.2
Hash for the release tag: 5d0bfb0c25082b61cb8830aa04ec34a13edccd31

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1147
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.2.2/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/rc/1.2.2/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

[RESULT][VOTE] Release Apache IoTDB 1.2.2

[Haonan Hou]

Hi all,

The release is approved by accepting 4 +1 votes:

3 from PMC members,
Jialin Qiao,
Gaofei Cao,
Yuan Tian.

1 from committer,
Qingxin Feng

Vote threads:

https://lists.apache.org/thread/gksw8so6hvfd417jsrvxq12yhohh2mdl
https://lists.apache.org/thread/543hq4wr9qzt9q6vbsyww82v7pzmf42h

Thanks,
Haonan Hou

[ANNOUNCE] Apache IOTDB 1.2.2 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.2.2.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.2.2 is the latest version of the v1 series. Feel free to upgrade
from 1.2.1 or earlier version.

## Features & Improvements

- [IOTDB-6029] Implementing flink-sql-iotdb-connector
- [IOTDB-6084] Pipe: support node-urls in connector-v1
- [IOTDB-6103] Adding count_time aggregation feature
- [IOTDB-6112] Limit & Offset push down doesn't take effect while there exist 
time filter
- [IOTDB-6115] Limit & Offset push down doesn't take effect while there exist 
null value
- [IOTDB-6120] push down limit/offset in query with group by time
- [IOTDB-6129] ConfigNode restarts without relying on Seed-ConfigNode
- [IOTDB-6131] Iotdb rest service supports insertRecords function
- [IOTDB-6151] Move DataNode's system.properties to upper dir
- [IOTDB-6173] Change default encoder of INT32 and INT64 from RLE to TS_2DIFF
- Adjust the default thrift timeout parameter to 60s
- Accelerate the deletion execution

## Bugs

- [IOTDB-6064] Pipe: Fix deadlock in rolling back procedures concurrently
- [IOTDB-6081] Pipe: use HybridExtractor instead of LogExtractor when realtime 
mode is set to log to avoid OOM under heavy insertion load
- [IOTDB-6145] Pipe: can not release TsFile or WAL resource after pipe is 
dropped
- [IOTDB-6146] Pipe: can not transfer data after 1000+ pipes' creating and 
dropping
- [IOTDB-6082] Improve disk space metrics
- [IOTDB-6104] tmp directory won't be cleaned after udf query end
- [IOTDB-6119] Add ConfigNode leader service check
- [IOTDB-6125] Fix DataPartition allocation bug when insert big batch data
- [IOTDB-6127] Pipe: buffered events in processor stage can not be consumed by 
connector
- [IOTDB-6132] CrossSpaceCompaction: The estimated memory size is too large for 
cross space compaction task
- [IOTDB-6133] NullPointerException occurs in unsequence 
InnerSpaceCompactionTask
- [IOTDB-6148] Pipe: Fixed the bug that some uncommited progresses may be 
reported
- [IOTDB-6156] Fixed TConfiguration invalidly in Thrift AsyncServer For 
IoTConsensus
- [IOTDB-6164] Can create illegal path through rest api
- Fix datanode status is ReadOnly because the disk is full
- Fix DataPartition allocation bug when insert big batch
- Fix flush point statistics
- Fix SchemaFileSketchTool is not found
- Refactoring DeleteOutdatedFileTask in WalNode
- Add compression and encoding type check for FastCompactionPerformer
- Add lazy page reader for aligned page reader to avoid huge memory cost when 
reading rows of aligned timeseries
- Pipe: use PipeTaskCoordinatorLock instead of ReentrantLock for multi thread 
sync
- Pipe: fix pipe procedure stuck because of data node async request forever 
waiting for response
- Pipe: fix NPE when HybridProgressIndex.updateToMinimumIsAfterProgressIndex 
after system reboot (DR: SimpleConsensus)
- Pipe: fix pipe coordinator deadlock causing CN election timeout
- Pipe: Improve performance for 1+ pipes
- RATIS-1873. Remove RetryCache assertion that doesn't hold

The full release note is available at:
https://dlcdn.apache.org/iotdb/1.2.2/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: Rollcall TsFile initial committers

[Haonan Hou]

Hi Jialin,

I would like to be the initial committer of TsFile.

I participated in the development of TsFile v2 for IoTDB 0.10.x and 0.11.x and 
the update tool for v1 to v2, v2 to v3.

Thanks
Haonan Hou

On 2023/10/17 03:40:42 Xinyu Tan wrote:
> Hi Jialin,
> 
> I would like to be the initial committer of TsFile.
> 
> I participated in the design and development of IoTDB 0.12 cluster version 
> combined with TsFile for incremental snapshot.
> 
> Now the consensus layer is designing a consensus algorithm based on TsFile 
> synchronization, which is expected to make TsFile more general in more 
> scenarios involving CDC and consensus.
> 
> Thanks
> 
> Xinyu Tan
> 
> On 2023/10/15 15:22:11 Jialin Qiao wrote:
> > Hi,
> > 
> > To make TsFile a TLP, we need to affirm the initial committer first.
> > The criteria for becoming the initial committer of TsFile is
> > prelimilary defined as meeting the following two conditions
> > simultaneously.
> > 
> > (1) Apache IoTDB PMC member
> > (2) Made contributions to the TsFile module
> > 
> > If you have made significant contributions to the TsFile module, you
> > can also apply to become an initial committer.
> > 
> > If you would like to be the initial committer of TsFile, please reply
> > to this email in 1 week :-)
> > 
> > Thanks,
> > —
> > Jialin Qiao
> > Apache IoTDB PMC
> > 
> 

Re: Rollcall TsFile initial committers

[Haonan Hou]

Hi Jialin,

I just find my name in list is not correct. It should be Haonan Hou, not Haohan 
Hou. ;)

Best,
Haonan


> On Nov 7, 2023, at 9:31 AM, Jialin Qiao  wrote:
> 
> Hi,
> 
> Welcome Dawei! We are still on naming search stage.
> The updated list:
> 
> Yuan Tian (jackiet...@apache.org)
> Chao Wang (wangchao...@apache.org)
> Christofer Dutz (cd...@apache.org)
> Jinrui Zhang (xingtan...@apache.org)
> Steve Yurong Su (r...@apache.org)
> Xinyu Tan (tanxi...@apache.org)
> Haohan Hou (hao...@apache.org)
> Gaofei Cao (gaogao...@apache.org)
> Jialin Qiao (qiaojia...@apache.org)
> Kun Liu (liu...@apache.org)
> Houliang Qi (neuyi...@apache.org)
> Xiangdong Huang (h...@apache.org)
> Chao Wang (ch...@apache.org)
> Jianmin Wang (jimw...@apache.org)
> Tian Jiang (jiangt...@apache.org）
> Xinyi Zhao (zhaoxi...@apache.org)
> Shuo Zhang (shuozh...@apache.org)
> Dawei Liu(li...@apache.org)
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> Dawei Liu  于2023年11月6日周一 21:09写道：
>> 
>> Hi,
>> Recently changed computer equipment, didn't check my email,
>> and found out that something very important was missing...
>> Can i still participate?
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Thanks,
>> —
>> Dawei Liu
>> Apache IoTDB PMC
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> At 2023-10-23 14:04:25, "Jialin Qiao"  wrote:
>>> Hi,
>>> 
>>> Welcome Shuo! The updated list:
>>> 
>>> Yuan Tian (jackiet...@apache.org)
>>> Chao Wang (wangchao...@apache.org)
>>> Christofer Dutz (cd...@apache.org)
>>> Jinrui Zhang (xingtan...@apache.org)
>>> Steve Yurong Su (r...@apache.org)
>>> Xinyu Tan (tanxi...@apache.org)
>>> Haohan Hou (hao...@apache.org)
>>> Gaofei Cao (gaogao...@apache.org)
>>> Jialin Qiao (qiaojia...@apache.org)
>>> Kun Liu (liu...@apache.org)
>>> Houliang Qi (neuyi...@apache.org)
>>> Xiangdong Huang (h...@apache.org)
>>> Chao Wang (ch...@apache.org)
>>> Jianmin Wang (jimw...@apache.org)
>>> Tian Jiang (jiangt...@apache.org）
>>> Xinyi Zhao (zhaoxi...@apache.org)
>>> Shuo Zhang (shuozh...@apache.org)
>>> 
>>> Thanks,
>>> —
>>> Jialin Qiao
>>> Apache IoTDB PMC
>>> 
>>> Shuo Zhang  于2023年10月23日周一 11:24写道：
>>> 
>>>> 
>>>> Hi Jialin,
>>>> 
>>>> I participated in the R&D of the early version of TsFile with our early 
>>>> teammates. Although my code contributions have lessened in recent years, I 
>>>> have continued to champion the file layer with the entire DB system. Going 
>>>> forward, I am happy to further promote TsFile and its development.
>>>> 
>>>> If you find it beneficial, I would be delighted to become one of the 
>>>> initial committers. Thanks a lot.
>>>> 
>>>> Best Regards,
>>>> 
>>>> 
>>>> Shuo ZHANG
>>>> zhangshu...@qq.com
>>>> 
>>>> From: Jialin Qiao
>>>> Date: 2023-10-15 23:22
>>>> To: dev
>>>> Subject: Rollcall TsFile initial committers
>>>> Hi,
>>>> 
>>>> To make TsFile a TLP, we need to affirm the initial committer first.
>>>> The criteria for becoming the initial committer of TsFile is
>>>> prelimilary defined as meeting the following two conditions
>>>> simultaneously.
>>>> 
>>>> (1) Apache IoTDB PMC member
>>>> (2) Made contributions to the TsFile module
>>>> 
>>>> If you have made significant contributions to the TsFile module, you
>>>> can also apply to become an initial committer.
>>>> 
>>>> If you would like to be the initial committer of TsFile, please reply
>>>> to this email in 1 week :-)
>>>> 
>>>> Thanks,
>>>> —
>>>> Jialin Qiao
>>>> Apache IoTDB PMC

CVE-2023-51656: Apache IoTDB: Unsafe deserialize map in Sync Tool

[Haonan Hou]

Severity: low

Affected versions:

- Apache IoTDB 0.13.0 through 0.13.4

Description:

Deserialization of Untrusted Data vulnerability in Apache IoTDB.This issue 
affects Apache IoTDB: from 0.13.0 through 0.13.4.

Users are recommended to upgrade to version 1.2.2, which fixes the issue.

References:

https://iotdb.apache.org
https://www.cve.org/CVERecord?id=CVE-2023-51656

[VOTE] Apache IoTDB 1.3.0 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.3.0 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.3.0
Hash for the release tag: fe787cac2ddd874b44482a80306d9d6ae333143c

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1154
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.3.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/v1.3.0/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

[RESULT][VOTE] Release Apache IoTDB 1.3.0

[Haonan Hou]

Hi all,

The release is approved by accepting 4 +1 votes:

3 from PMC members,
Jialin Qiao,
Gaofei Cao,
Xinyu Tan.

1 from committer,
Qingxin Feng

Vote threads:

https://lists.apache.org/thread/zs0md2pm5k4vnby3bk5nsycgpddoczvl


Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.3.0 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.3.0.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.3.0 is the latest version of the v1 series. Feel free to upgrade
from earlier version.

## Features & Improvements

- Optimize the permission module and support timeseries permission control
- Optimize heap and off-heap memory configuration in startup script
- Computed-type view timeseries support LAST queries
- Add pipe-related monitoring metrics
- Pipe rename 'Extractor' to 'Source' and 'Connector' to 'Sink'
- [IOTDB-6138] Support Negative timestamp
- [IOTDB-6193] Reject Node startup when loading configuration file failed
- [IOTDB-6194] Rename target_config_node_list to seed_config_node
- [IOTDB-6200] Change schema template to device template
- [IOTDB-6207] Add Write Point Metrics for load function
- [IOTDB-6208] Node error detection through broken thrift pipe
- [IOTDB-6217] When the number of time series reaches the upper limit, the 
prompt message should be changed to prioritize using device templates
- [IOTDB-6218] Rename storage_query_schema_consensus_free_memory_proportion to 
datanode_memory_proportion
- [IOTDB-6219] Fix the display problem of explain that the print result is not 
aligned
- [IOTDB-6220] Pipe: Add check logic to avoid self-transmission
- [IOTDB-6222] Optimize the performance of Python client
- [IOTDB-6230] Add HEAPDUMP configuration in datanode-env.sh
- [IOTDB-6231]SchemaCache supports precise eviction
- [IOTDB-6232] Adding SSL function to dn_rpc_port

## Bugs

- [IOTDB-6160] while using ` in target path, select into will throw error
- [IOTDB-6167] DataNode can't register to cluster when fetch system 
configuration throws NPE
- [IOTDB-6168] ConfigNode register retry logic does not worked
- [IOTDB-6171] NPE will be thrown while printing FI with debug on
- [IOTDB-6184] Merge Sort finishes one iterator too long
- [IOTDB-6191] Fix group by year not considering leap years
- [IOTDB-6226] Fix the problem of inaccurate GC monitor detection at the 
beginning and adjusting the alert threshold
- [IOTDB-6239] Show regions display error create time

The full release note is available at:
https://dlcdn.apache.org/iotdb/1.3.0/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

CVE-2023-46226: Apache IoTDB: Remote Code Execution (RCE) risk via the UDF

[Haonan Hou]

Severity: moderate

Affected versions:

- Apache IoTDB 1.0.0 through 1.2.2

Description:

Remote Code Execution vulnerability in Apache IoTDB.This issue affects Apache 
IoTDB: from 1.0.0 through 1.2.2.

Users are recommended to upgrade to version 1.3.0, which fixes the issue.

Credit:

Glassy of EagleCloud (finder)

References:

https://iotdb.apache.org
https://www.cve.org/CVERecord?id=CVE-2023-46226

Re: Build issues on GitHub Actions

[Haonan Hou]

Hi,

Let me fix it later. It’s easy to fix.

Best,
Haonan

> On Mar 27, 2024, at 1:58 AM, Christofer Dutz  
> wrote:
> 
> Hi all,
> 
> So, it seems that building the CPP parts is currently failing on GitHub 
> Actions, as the pre-compiled thrift executables seems to have been compiled 
> on MacOS 13 however the GitHub Actions runners are still on MacOS 12.
> 
> CHris

Re: Build issues on GitHub Actions

[Haonan Hou]

Ok, Yuheng has fixed the problem. Details see [1].

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

Haonan

> On Mar 27, 2024, at 1:58 AM, Christofer Dutz  
> wrote:
> 
> Hi all,
> 
> So, it seems that building the CPP parts is currently failing on GitHub 
> Actions, as the pre-compiled thrift executables seems to have been compiled 
> on MacOS 13 however the GitHub Actions runners are still on MacOS 12.
> 
> CHris

[VOTE] Apache IoTDB 1.3.1 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.3.1 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.3.1
Hash for the release tag: 8759b1e520105462ba13c8b35df6e516b056a281

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1155
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.3.1/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/v1.3.1/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Re: Inconsistency in query results based on the environment

[Haonan Hou]

Hi Cheongu,

The images are not allowed to show on the email list, therefore we cannot see 
them here.
Would you like to repost your issue on github [1]? Thanks.

Best,
Haonan Hou
[1] https://github.com/apache/iotdb/issues

On 2024/04/03 02:28:32 김천구 wrote:
> Hi all,
> 
> I'm currently using version 1.2.2 of iotdb, and there seems to be an issue
> with the database query results. The results from executing queries via the
> Python API and running queries in the CLI environment using start-cli.sh
> are inconsistent. In the CLI environment, executing the query "time >=
> 2008-02-02T14:00:40 and time < 2008-02-02T14:00:41" returns 38 results,
> while when executed via Python, it returns 33 results.
> [image: image.png]
> [image: 27387e12-f71a-4af3-acca-b594000ed146.png]
> 
> Conversely, when applying the condition "time >= 2008-02-02T17:30:00 and
> time < 2008-02-02T17:30:01," the CLI environment returns 44 results,
> whereas Python returns 50 results.
> [image: image.png]
> [image: image.png]
> As you can see, the timestamp 120194460049 ("2008-02-02T18:30:00.049") is
> not included in the output of the CLI query. However, when searching with
> the condition "time = 1201944600049," the corresponding tuple is returned.
> [image: image.png]
> I don't understand why this issue is occurring. Would changing the version
> resolve the issue?
> 
> Best,
> 
> Cheongu Kim
> 

Archive apache/iotdb-web-workbench repo?

[Haonan Hou]

Hi all,

We received some security issues about apache/iotdb-web-workbench recently. 
However, we don't have enough maintainers to fix them. The repo has no new 
commit since Apr 3, 2023. There is an option that we can archive that repo.

Any idea?

Best,
Haonan Hou

Re: 答复: Splitting up the repos

[Haonan Hou]

+1

Haonan

On 2024/04/17 08:46:16 Wang Critas wrote:
> The examples could be classified into two parts
> (1) Connector example: flink, hadoop, kafka, pulsar, rabiitmq, rocketmq
> (2) IoTDB native api example: jdbc, mqtt, pipe, rest, schema, session,
> trigger, udf
> 
> For (1), we could move into extra repo.
> For (2) , they should be retained in the IoTDB repo.
> 
> Jialin Qiao
> 
> 
> Hi
> 
> if we were to vote on this (which we can) I would vote +1 on ‘ The examples 
> could be classified into two parts '
> 
> Voting will be open for 72hr.
> A minimum of 3 binding +1 votes and more binding +1 than binding -1
> are required to pass.
> You can achieve the above by following [4].
> [ ] +1 accept
> [ ] -1 reject (explanation required)
> 
> Xuan
> 
> 发件人: Christofer Dutz 
> 日期: 星期三, 2024年4月17日 16:38
> 收件人: dev@iotdb.apache.org 
> 主题: AW: Splitting up the repos
> We however still need this to be decided.
> 
> Currently we have something such as one binding vote for keeping the examples 
> together and one for splitting it up.
> I have no objections to splitting it up, but we need to do things the Apache 
> way here …
> 
> Otherwise this would imply that there are votes that count more than others 
> and we need to make sure this impression is not made.
> 
> Chris
> 
> 
> Von: Wang Critas 
> Datum: Mittwoch, 17. April 2024 um 10:20
> An: dev@iotdb.apache.org 
> Betreff: 答复: Splitting up the repos
> In here
> https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fiotdb-extras%2Fpull%2F6&data=05%7C02%7C%7C0ef2e475da4d43765f3c08dc5eb9c496%7C84df9e7fe9f640afb435%7C1%7C0%7C638489399201851637%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=5Thiae%2BMRGzDZ6vklThuZO4GuXomaIntuyh%2BIuC3eq0%3D&reserved=0
> 
> 发件人: Christofer Dutz 
> 日期: 星期一, 2024年4月15日 21:01
> 收件人: dev@iotdb.apache.org 
> 主题: AW: Splitting up the repos
> Well,
> 
> as I said … I’ve already done the work of splitting things up (I had waited 5 
> days for any comments here)
> 
> If we would now do it differently, I am sure someone would be able to re-do 
> the split based on my work and then simply delete the double examples from 
> the extras repo.
> 
> So, I would be voting for moving all examples to the extras, you for 
> splitting the examples, guess we need at least a third vote (with hopefully 
> not a 3rd opinion ;-) )
> 
> Chris
> 
> 
> Von: Jialin Qiao 
> Datum: Montag, 15. April 2024 um 14:38
> An: dev@iotdb.apache.org 
> Betreff: Re: Splitting up the repos
> Hi,
> 
> The examples could be classified into two parts
> (1) Connector example: flink, hadoop, kafka, pulsar, rabiitmq, rocketmq
> (2) IoTDB native api example: jdbc, mqtt, pipe, rest, schema, session,
> trigger, udf
> 
> For (1), we could move into extra repo.
> For (2) , they should be retained in the IoTDB repo.
> 
> Jialin Qiao
> 
> Christofer Dutz  于2024年4月15日周一 17:56写道：
> >
> > Hmpf,
> >
> > a little bit sooner reply would have been good … I’m already done with the 
> > changes, also with moving all examples and the parts of the distribution 
> > bundling the connectors.
> >
> > I do think also moving the examples is a good idea. Usually, examples pull 
> > in all sorts of dependencies, which show up on vulnerability reports. Also 
> > do we have some examples that refer to stuff we now moved out of the main 
> > repo, we’d be getting a cyclic dependency from that, so we would have to 
> > split up the examples in that case.
> >
> > So, if we were to vote on this (which we can) I would vote +1 on moving all 
> > examples out of the main repo.
> >
> > Chris
> >
> >
> > Von: Jialin Qiao 
> > Datum: Montag, 15. April 2024 um 11:20
> > An: dev@iotdb.apache.org 
> > Betreff: Re: Splitting up the repos
> > Hi,
> >
> > 1. Which Parts: Only iotdb-connector need to be moved,  distribution
> > and examples will impact the release and users.
> > 2. How to split up:  I prefer【Simply ignore the history, copy the
> > files to the new repo and delete them from the old】.
> >
> > Jialin Qiao
> >
> > Christofer Dutz  于2024年4月15日周一 16:27写道：
> > >
> > > Hi all,
> > >
> > >
> > > So, I’ve set a tag on the main repository “before-moving-extras” 
> > > (https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fiotdb%2Freleases%2Ftag%2Fbefore-moving-extras&data=05%7C02%7C%7C0ef2e475da4d43765f3c08dc5eb9c496%7C84df9e7fe9f640afb435%7C1%7C0%7C638489399201859843%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=9avY%2FHekomDIBORka2KgTSSMTkhvBR%2F3%2FfEEFV5rlTU%3D&reserved=0

Re: Archive apache/iotdb-web-workbench repo?

[Haonan Hou]

Ok, the repo has archived. Now the repo is read-only.

Haonan Hou



On 2024/04/18 06:42:51 Christofer Dutz wrote:
> +1 for archiving it.
> 
> Perfect would be, that we address the issues, then release it and announce 
> it's retirement. But if we don't have the capacity to fix them, then retiring 
> the module is better than leaving it.
> 
> Chris
> 
> Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> 
> From: Jialin Qiao 
> Sent: Thursday, April 18, 2024 5:30:37 AM
> To: dev@iotdb.apache.org 
> Subject: Re: Archive apache/iotdb-web-workbench repo?
> 
> +1 for archive
> 
> 
> Jialin Qiao
> 
> Haonan Hou  于2024年4月18日周四 11:23写道：
> >
> > Hi all,
> >
> > We received some security issues about apache/iotdb-web-workbench recently. 
> > However, we don't have enough maintainers to fix them. The repo has no new 
> > commit since Apr 3, 2023. There is an option that we can archive that repo.
> >
> > Any idea?
> >
> > Best,
> > Haonan Hou
> 

[VOTE] Apache IoTDB 1.3.1 RC2 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.3.1 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.3.1
Hash for the release tag: 214695df59915884ca43767f944ed7b921763864

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1157
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.3.1/rc2
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
[5] https://github.com/apache/iotdb/blob/v1.3.1/RELEASE_NOTES.md
[6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS

Best,

Haonan Hou

Re: [VOTE] Apache IoTDB 1.3.1 RC2 release

[Haonan Hou]

Hi,

+1 (binding)

The source release:
apache headers [ok]
signatures and hashes [ok]
LICENSE and NOTICE [ok]
no jar files [ok]
could compile from source: ./mvnw.sh clean install [ok]

The binary distribution:
version number in CLI [ok]
signatures and hashes [ok]
start in mac, jdk8 [ok]
statements executed successfully: [ok]

SET STORAGE GROUP TO root.turbine;
CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
insert into root.turbine.d1(timestamp,s0) values(1,1);
insert into root.turbine.d1(timestamp,s0) values(2,2);
insert into root.turbine.d1(timestamp,s0) values(3,3);
insert into root.turbine.d2(time,s0) values(now(),1);
insert into root.turbine.d2(time,s0) values(now(),2);
insert into root.turbine.d2(time,s0) values(now(),3);
select ** from root;
select ** from root align by device;


Best,
Haonan Hou

On 2024/04/22 01:59:58 Jialin Qiao wrote:
> Hi,
> 
> +1 (binding)
> 
> The source release:
> apache headers [ok]
> signatures and hashes [ok]
> LICENSE and NOTICE [ok]
> no jar files [ok]
> could compile from source: ./mvnw.sh clean install [ok]
> 
> The binary distribution:
> version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk8 [ok]
> statements executed successfully:  [ok]
> 
> SET STORAGE GROUP TO root.turbine;
> CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
> insert into root.turbine.d1(timestamp,s0) values(1,1);
> insert into root.turbine.d1(timestamp,s0) values(2,2);
> insert into root.turbine.d1(timestamp,s0) values(3,3);
> insert into root.turbine.d2(time,s0) values(now(),1);
> insert into root.turbine.d2(time,s0) values(now(),2);
> insert into root.turbine.d2(time,s0) values(now(),3);
> select ** from root;
> select ** from root align by device;
> 
> 
> Jialin Qiao
> 
> Yuan Tian  于2024年4月22日周一 08:52写道：
> >
> > Hi,
> >
> > +1 (binding)
> >
> > The source release:
> > apache headers [ok]
> > signatures and hashes [ok]
> > LICENSE and NOTICE [ok]
> > no jar files [ok]
> > could compile from source: ./mvnw.sh clean install [ok]
> >
> > The binary distribution:
> > version number in CLI [ok]
> > signatures and hashes [ok]
> > start in mac, jdk8 [ok]
> > statements executed successfully:  [ok]
> >
> > SET STORAGE GROUP TO root.turbine;
> > CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=GORILLA;
> > insert into root.turbine.d1(timestamp,s0) values(1,1);
> > insert into root.turbine.d1(timestamp,s0) values(2,2);
> > insert into root.turbine.d1(timestamp,s0) values(3,3);
> > insert into root.turbine.d2(time,s0) values(now(),1);
> > insert into root.turbine.d2(time,s0) values(now(),2);
> > insert into root.turbine.d2(time,s0) values(now(),3);
> > select ** from root;
> > select ** from root align by device;
> >
> >
> > Best,
> > -
> > Yuan Tian
> >
> > On Fri, Apr 19, 2024 at 5:14 PM Haonan Hou  wrote:
> >
> > > Hi all,
> > >
> > > Apache IoTDB 1.3.1 has been staged under [2] and it’s time to vote
> > > on accepting it for release. All Maven artifacts are available under [1].
> > > Voting will be open for 72hr.
> > > A minimum of 3 binding +1 votes and more binding +1 than binding -1
> > > are required to pass.
> > >
> > > Release tag: v1.3.1
> > > Hash for the release tag: 214695df59915884ca43767f944ed7b921763864
> > >
> > > Before voting +1, PMC members are required to download
> > > the signed source code package, compile it as provided, and test
> > > the resulting executable on their own platform, along with also
> > > verifying that the package meets the requirements of the ASF policy
> > > on releases. [3]
> > >
> > > You can achieve the above by following [4].
> > >
> > > [ ] +1 accept (indicate what you validated - e.g. performed the
> > > non-RM items in [4])
> > > [ ] -1 reject (explanation required)
> > >
> > >
> > > [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1157
> > > [2] https://dist.apache.org/repos/dist/dev/iotdb/1.3.1/rc2
> > > [3] https://www.apache.org/dev/release.html#approving-a-release
> > > [4]
> > > https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> > > [5] https://github.com/apache/iotdb/blob/v1.3.1/RELEASE_NOTES.md
> > > [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> > >
> > > Best,
> > >
> > > Haonan Hou
> > >
> 

[RESULT][VOTE] Release Apache IoTDB 1.3.1

[Haonan Hou]

Hi all,

The release is approved by accepting 3 +1 votes:

3 from PMC members,
Jialin Qiao,
Yuan Tian,
Haonan Hou.

Vote threads:

https://lists.apache.org/thread/kzhb0j419339ncs8615zdzlx1rkm4z73


Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.3.1 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.3.1.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.3.1 is the latest version of the v1 series. Feel free to upgrade
from earlier version.

## Features & Improvements

- Add cluster script for one-click start-stop (start-all/stop-all.sh & 
start-all/stop-all.bat)
- Add script for one-click instance information collection (collect-info.sh & 
collect-info.bat)
- Add new statistical aggregators include stddev and variance
- Add repair tsfile data command
- Support setting timeout threshold for Fill clause. When time beyond the 
threshold, do not fill value.
- Simplify the time range specification for data synchronization, directly set 
start and end times
- Improved system observability (adding dispersion monitoring of cluster nodes, 
observability of distributed task scheduling framework)
- Optimized default log output strategy
- Enhance memory control for Load TsFile, covering the entire process
- Rest API (Version 2) adds column type return.
- Improve the process of query execution
- Session automatically fetch all available DataNodes
  ...
## Bugs

- Fix issue with abnormal behavior when time precision is not in milliseconds 
during grouping by month.
- Fix issue with abnormal behavior when duration contains multiple units during 
grouping by month.
- Fix bug where limit and offset cannot be pushed down when there is an order 
by clause.
- Fix abnormal behavior in combination scenario of grouping by month + align by 
device + limit.
- Fix deserialization errors during IoT protocol synchronization.
- Fix concurrent exceptions in deleting timeseries.
- Fix issue where group by level in view sequences does not execute correctly.
- Fix potential issue of metadata creation failure when increasing election 
timeout.

The full release note is available at:
https://dlcdn.apache.org/iotdb/1.3.1/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector,
Hadoop-connector, Hive-connector and Flink-connector can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

Re: AW: Possible fix for randomly failing Jenkins builds

[Haonan Hou]

Approved and merged. 
Thanks.

Haonan

On 2024/05/17 10:14:10 Christofer Dutz wrote:
> Done:
> https://github.com/apache/iotdb/pull/12542
> Waiting for approval.
> 
> Chris
> 
> Von: Jialin Qiao 
> Datum: Freitag, 17. Mai 2024 um 09:15
> An: dev@iotdb.apache.org 
> Betreff: Re: Possible fix for randomly failing Jenkins builds
> +1 for importing the solutions in PLC4X
> 
> 
> Jialin Qiao
> 
> Christofer Dutz  于2024年5月14日周二 23:32写道：
> >
> > Hi all,
> >
> > I know that in IoTDB as well as PLC4X we were having issues of regularly 
> > but randomly failing Jenkins builds.
> >
> > Usually, these problems were because of timeouts when deploying to Nexus.
> >
> > In PLC4X I have now tried something that seems to be doing the job … 
> > possibly this could also help us here (I mean … the biggest part of the 
> > Jenkins setup is borrowed from PLC4X anyway ;-) )
> >
> > My solution was to wrap the execution of the deploy step in a loop on bash 
> > level:
> >
> > https://github.com/apache/plc4x/blob/develop/Jenkinsfile#L167
> >
> > sh 'until ./mvnw -f jenkins.pom -X -P deploy-snapshots 
> > wagon:upload || (( count++ >= 5 )); do echo "Retrying to deploy"; done'
> >
> > So, it would try up to 5 times, if deployment fails.
> >
> > I think in case of deployment the full build is done and was successful. 
> > The only reason for failures in this step usually is problems with Nexus 
> > and a stupid retry should help.
> >
> > What do you think? Should we try the same change?
> >
> >
> > Chris
> 

Re: [DISCUSS] Investigate updating to Thrift 0.20.0?

[Haonan Hou]

Hi,

I tried to upgrade Thrift 0.19.0 last year[1], and I think there is no 
compatibility issue if the client side still using the current v0.14.1.

Maybe we need to do more performance tests?

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

Haonan

> On May 28, 2024, at 3:40 AM, Christofer Dutz  
> wrote:
> 
> Hi all,
> 
> while doing some experiments over the weekend I came to notice that Thrift 
> 0.19.0 and above is again compatible with Java 8 … this was the major reason 
> for us not updating to versions without CVEs.
> I’ve tried out 0.20.0 and my local fork of IoTDB runs perfectly with it.
> 
> https://github.com/apache/thrift/blob/master/CHANGES.md
> 
> Might be worth investigating to update? I’ve already got an up-to-date 
> version of the thrift compiler … if we wanted to try it out, I could stage 
> release versions for:
> 
> 
>  *   Mac – aarch64
>  *   Mac – x86_64
>  *   Linux  – aarch64
>  *   Linux  – x86_64
>  *   Windows  – aarch64
>  *   Windows  – x86_64
> 
> Chris

Re: [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0)

[Haonan Hou]

+1

Haonan Hou

On 2024/05/28 14:40:39 Christofer Dutz wrote:
> Hi all,
> 
> I after fixing some issues in the cmake-maven-plugin, have I updated the 
> iotdb-bin-resources module to use these.
> Now we can stage Apache Thrift binaries for all platforms.
> 
> In order to test, if Apache Thrift 0.20.0 (Which is Java 8 compatible again), 
> I also updated the Thrift version and staged a release of Thrift binaries for 
> all of our supported platforms in Nexus.
> 
> I’ve staged the artifacts at:
> https://repository.apache.org/content/repositories/orgapacheiotdb-1158
> 
> Tag Name: iotdb-tools-thrift-v0.20.0.0
> https://github.com/apache/iotdb-bin-resources/releases/tag/iotdb-tools-thrift-v0.20.0.0
> 
> The source bundle generally consists of a pom.xml and an assembly xml … so it 
> should be quick to review.
> https://repository.apache.org/content/repositories/orgapacheiotdb-1158/org/apache/iotdb/tools/iotdb-tools-thrift/0.20.0.0/iotdb-tools-thrift-0.20.0.0-source-release.zip
> 
> I’m intentionally not staging it on the release-svn, as nobody should be 
> required to consume this module but us ourselves.
> 
> The vote stays open for 72hours … assuming enough support, I’ll then finish 
> changing the main repo to use these artifacts.
> 
> 
> Chris
> 

Prepare releasing 1.3.2?

[Haonan Hou]

Hi all,

IoTDB v1.3.1 has released over 1 month. In this month, we did a lot over bug 
fixes and improvements. I think we can start the process of releasing new 
version.

If we all agree, I'm going to checkout the rc/1.3.2 branch and bump the version 
of master branch to 1.3.3-SNAPSHOT.

BR,
Haonan

Re: [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0)

[Haonan Hou]

Hi Chris,

I think 72 hours has passed. These artifacts can be released now?

Thanks,
Haonan

On 2024/05/28 14:40:39 Christofer Dutz wrote:
> Hi all,
> 
> I after fixing some issues in the cmake-maven-plugin, have I updated the 
> iotdb-bin-resources module to use these.
> Now we can stage Apache Thrift binaries for all platforms.
> 
> In order to test, if Apache Thrift 0.20.0 (Which is Java 8 compatible again), 
> I also updated the Thrift version and staged a release of Thrift binaries for 
> all of our supported platforms in Nexus.
> 
> I’ve staged the artifacts at:
> https://repository.apache.org/content/repositories/orgapacheiotdb-1158
> 
> Tag Name: iotdb-tools-thrift-v0.20.0.0
> https://github.com/apache/iotdb-bin-resources/releases/tag/iotdb-tools-thrift-v0.20.0.0
> 
> The source bundle generally consists of a pom.xml and an assembly xml … so it 
> should be quick to review.
> https://repository.apache.org/content/repositories/orgapacheiotdb-1158/org/apache/iotdb/tools/iotdb-tools-thrift/0.20.0.0/iotdb-tools-thrift-0.20.0.0-source-release.zip
> 
> I’m intentionally not staging it on the release-svn, as nobody should be 
> required to consume this module but us ourselves.
> 
> The vote stays open for 72hours … assuming enough support, I’ll then finish 
> changing the main repo to use these artifacts.
> 
> 
> Chris
> 

Re: Prepare releasing 1.3.2?

[Haonan Hou]

Ok, the version of master branch has updated to 1.3.3-SNAPSHOT.
Once Ratis 3.1.0 released, I'll prepare the rc/1.3.2 branch. 

Best,
Haonan


On 2024/06/03 02:07:55 Xinyu Tan wrote:
> Hi haonan
> 
> +1 for bumping the version of master branch to 1.3.3-SNAPSHOT.
> 
> As for the 1.3.2 release, currently ratis is releasing there new version 
> 3.1.0[1], we can rely on the official Ratis 3.1.0 release in the open source 
> version IoTDB 1.3.2 instead of the snapshot release to conform to the 
> guidelines of the Apache community.
> 
> Best
> -
> Xinyu Tan
> 
> [1] https://lists.apache.org/thread/q8gdfz1j1l4qv1v24z4dxcg01j9qs28n
> 
> On 2024/06/03 01:44:17 Haonan Hou wrote:
> > Hi all,
> > 
> > IoTDB v1.3.1 has released over 1 month. In this month, we did a lot over 
> > bug fixes and improvements. I think we can start the process of releasing 
> > new version.
> > 
> > If we all agree, I'm going to checkout the rc/1.3.2 branch and bump the 
> > version of master branch to 1.3.3-SNAPSHOT.
> > 
> > BR,
> > Haonan
> > 
> 

Re: AW: version about odbc

[Haonan Hou]

There is another example of the rest-client-c-example without the pom.xml that 
demonstrate how to use rest api with c language. Should we consider it as 
document example, or a "compilable" example? 

I prefer it is a compilable module and I think it is possible to add a pom.xml 
and make it as a maven module.

Haonan

On 2024/06/07 10:20:21 Christofer Dutz wrote:
> The ODBC is not really a “compilable” example.
> It contains a description how you can use a commercial product to wrap our 
> JDBC driver in order to produce an ODBC driver.
> Also does it contain a compilable C# project file, that demonstates the usage 
> of the ODBC API.
> 
> However even if the example would be compiled as part of the build, you would 
> still need to manually prepare the ODBC wrapper.
> 
> I would consider this module more documentation than “compilable code”.
> 
> Chris
> 
> 
> Von: Yuan Tian 
> Datum: Freitag, 7. Juni 2024 um 12:14
> An: dev 
> Betreff: version about odbc
> Hi all,
> 
> I found that in master branch, we've already upgraded the version to 
> 1.3.3-SNAPSHOT, but the examples about odbc module is missed?
> 
> [cid:ii_lx4j3xy50]
> 
> Best regards,
> -
> Yuan Tian
> 

Allow the client with python 3.6 to use IoTDB

[Haonan Hou]

Hi,

The current python client of IoTDB requires the python version >= 3.7.
However, I met some applications running on some old platforms which only 
support python 3.6, and I found it is easy to make the adaption. Here is the 
PR[1].

In this PR, I also added a CI with python 3.6 and it can work correctly. It 
would be good if I can get some approval.

Haonan Hou

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

[VOTE] Apache IoTDB 1.3.2 RC1 release

[Haonan Hou]

Hi all,

Apache IoTDB 1.3.2 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: v1.3.2
Hash for the release tag: aa0ff4adf2fe00368b2145dd5f561d30df06a885

Before voting +1, PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases. [3]

You can achieve the above by following [4].

[ ] +1 accept (indicate what you validated - e.g. performed the
non-RM items in [4])
[ ] -1 reject (explanation required)


[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1159
[2] https://dist.apache.org/repos/dist/dev/iotdb/1.3.2/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release

Best,

Haonan Hou

Re: Allow the client with python 3.6 to use IoTDB

[Haonan Hou]

Ok, this PR has been merged.

Best,
Haonan

On 2024/06/24 14:19:36 Haonan Hou wrote:
> Hi,
> 
> The current python client of IoTDB requires the python version >= 3.7.
> However, I met some applications running on some old platforms which only 
> support python 3.6, and I found it is easy to make the adaption. Here is the 
> PR[1].
> 
> In this PR, I also added a CI with python 3.6 and it can work correctly. It 
> would be good if I can get some approval.
> 
> Haonan Hou
> 
> [1] https://github.com/apache/iotdb/pull/12792
> 

[RESULT][VOTE] Release Apache IoTDB 1.3.2

[Haonan Hou]

Hi all,

The release is approved by accepting 3 +1 votes:

3 from PMC members,
Qingxin Feng,
Christofer Dutz,
Jialin Qiao.

Vote threads:

https://lists.apache.org/thread/svdkp2gqy960t9svpmygp4hdjcdnoswo


Thanks,
Haonan Hou

[ANNOUNCE] Apache IoTDB 1.3.2 released

[Haonan Hou]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.3.2.

Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.

Apache IoTDB 1.3.2 is the latest version of the v1 series. Feel free to upgrade
from earlier version.

## Features & Improvements
- Storage Module: Performance improvement in the insertRecords interface for 
writing
- Query Module: New Explain Analyze statement added (monitoring the time spent 
on each stage of a single SQL execution)
- Query Module: New UDAF (User-Defined Aggregate Function) framework added
- Query Module: New MaxBy/MinBy functions added, supporting the retrieval of 
maximum/minimum values along with the corresponding timestamps
- Query Module: Performance improvement in value filtering queries
- Data Synchronization: Path matching supports path pattern
- Data Synchronization: Supports metadata synchronization (including time 
series and related attributes, permissions, etc.)
- Stream Processing: Added Alter Pipe statement, supporting hot updates of 
plugins for Pipe tasks
- System Module: System data point count statistics now include statistics for 
data imported by loading TsFile
- Scripts and Tools: New local upgrade backup tool added (backing up original 
data through hard links)
- Scripts and Tools: New export-data/import-data scripts added, supporting data 
export in CSV, TsFile formats or SQL statements
- Scripts and Tools: Windows environment now supports distinguishing 
ConfigNode, DataNode, and Cli by window name
...
## Bugs
- Optimize the error message when a NullPointerException (NPE) occurs due to a 
timeout when dropping a database.
- Add logs for notifyLeaderReady, notifyLeaderChanged, and procedure worker.
- Add compatibility handling for existing erroneous data during file merging.
- Fix the deadlock issue caused by flushing empty files during querying.
- Fix the issue where Ratis becomes unresponsive during read, write, and delete 
operations.
- Fix the concurrent bug in load and merge operations.
- Fix the issue where the system's compression ratio is recorded as a negative 
number in the file for certain scenarios.
- Fix the ConcurrentModificationException issue during memory estimation for 
merge tasks.
- Fix potential deadlocks that may occur when writing, automatically creating, 
and deleting databases concurrently.
...

The full release note is available at:
https://raw.githubusercontent.com/apache/iotdb/rc/1.3.2/RELEASE_NOTES.md

The release is available for download at:
http://iotdb.apache.org/Download

Maven artifacts for JDBC driver, session SDK, TsFile SDK can be found at:
https://search.maven.org/search?q=3Dg:org.apache.iotdb


Regards,
The Apache IoTDB team

CVE-2024-36448: Apache IoTDB Workbench: SSRF Vulnerability (EOL)

[Haonan Hou]

Severity: low

Affected versions:

- Apache IoTDB Workbench 0.13.0 or later

Description:

** UNSUPPORTED WHEN ASSIGNED ** Server-Side Request Forgery (SSRF) 
vulnerability in Apache IoTDB Workbench.

This issue affects Apache IoTDB Workbench: from 0.13.0.

As this project is retired, we do not plan to release a version that fixes this 
issue. Users are recommended to find an alternative or restrict access to the 
instance to trusted users.

NOTE: This vulnerability only affects products that are no longer supported by 
the maintainer.

Credit:

L0ne1y (finder)

References:

https://iotdb.apache.org
https://www.cve.org/CVERecord?id=CVE-2024-36448

Re: Upgrading version from 1.4.0-SNAPSHOT to 2.0.0-SNAOSHOT for master branch

[Haonan Hou]

+1

BR,
Haonan

On 2024/08/30 06:43:04 Gaofei Cao wrote:
> +1 for V2.0.0.
> 
> Table model is significantly different from Tree model, besides the
> differences of the data modeling, insert sql and query sql,
> table model also brings lots of features such as Join, SubQuery and
> Window Function which is not included in tree model.
> 
> -
> Gaofei Cao
> 
> Wang Critas  于2024年8月30日周五 13:07写道：
> >
> > Hi all,
> >
> > It seems that version 2.0 is more suitable, as it introduces a completely 
> > new table model.
> >
> > +1 for version 2.0
> > -
> > Xuan Wang
> >
> > 发件人: Yuan Tian 
> > 日期: 星期一, 2024年8月26日 14:14
> > 收件人: dev@iotdb.apache.org 
> > 主题: Re: Upgrading version from 1.4.0-SNAPSHOT to 2.0.0-SNAOSHOT for master 
> > branch
> > yes, I forgot about the AINode which will also be developed in V2.0.0
> >
> > On Mon, Aug 26, 2024 at 1:57 PM Jialin Qiao  wrote:
> >
> > > Hi,
> > >
> > > In previous years, we mainly focus on Data Management (Insertion &
> > > Storage & Synchronization & Simple query on one series).
> > >
> > > If we summarize the ongoing works of IoTDB, we will find the Relation
> > > module (Query across multi timeseries), AINode (Predict the trend of
> > > timeseries) are all for enhancing the Data Analysis.
> > >
> > > So, a major version bump looks acceptable, indicating IoTDB enters a
> > > new phase from Data Management to Data Analysis.
> > >
> > > Jialin Qiao
> > >
> > > Stefanie Zhao  于2024年8月26日周一 12:29写道：
> > > >
> > > > Hi Chris,
> > > >
> > > > I really appreciate that there is such a discussion on the version
> > > number of IoTDB in the community, and here are some of my thoughts.
> > > >
> > > > I believe that upgrading the first version number requires consideration
> > > of various impacts. The compatibility of interfaces between versions is 
> > > one
> > > aspect. At the same time, it is also necessary to consider whether the
> > > improvements of the version will have a significant impact on other 
> > > aspects
> > > of the system, such as stability and maturity. These are also important
> > > factors that users pay attention to, so we want to make our users perceive
> > > this through the upgrade from 1.x to 2.0.
> > > >
> > > > Involving table model to IoTDB has the following specific changes:
> > > > 1. Milestone changes in functionality: With the addition of the table
> > > model, IoTDB will have two sets of metadata models. This is an important
> > > large-scale update of a module, representing that IoTDB will be able to
> > > support and connect with traditional developer habits in the future, which
> > > will have a milestone impact on users.
> > > > 2. Upgrade of code architecture: Due to the table model, IoTDB's data
> > > file has been upgraded from TsFile v3 to v4, which involves adjustments to
> > > the file structure. And also, we add a query engine for the table model.
> > > These are all major upgrades to code architecture.
> > > > 3. Extensive impact and changes to the code: Although we are still in
> > > the development stage of the table model, just the first PR[13119], the
> > > table model has affected 1266 files (out of a total of 5943 Java files),
> > > involving 116973 lines+ and 13196 lines- of code. This scope of code 
> > > impact
> > > far exceeds the impact range of an ordinary feature.
> > > > 4. Impact on system stability and maturity: Although we will strive to
> > > reduce the impact of the above extensive functional changes and code
> > > modifications on the performance and stability of the entire system, as
> > > software developers, we all understand that achieving the above goals 
> > > still
> > > requires some time to mature, and the impact on stability is also part of
> > > what users perceive.
> > > >
> > > > I have also looked at some requirments of the upgrade of the first
> > > version number in Apache projects, but it seems that there is no clear
> > > standard. The introduction of incompatibilities in features or interfaces
> > > you mentioned is indeed an important consideration (Spark also explicitly
> > > mentions it, Apache Spark Release 3.0.0), but more importantly, it is
> > > whether developers want to convey to users "this is a major version 
> > > change,
> > > which may have a significant impact on users." So, like other Apache
> > > projects (such as Apache Doris), they will also consider architectural
> > > upgrades, changes in metadata, or underlying data formats as factors for
> > > upgrading the first version number (Apache Doris Release Versioning).
> > > >
> > > > So we still hope that the table model version number will make its debut
> > > to our users as version 2.0.
> > > >
> > > > -
> > > > Best, Stefanie
> > > >
> > > > On 2024/08/25 07:40:50 Christofer Dutz wrote:
> > > > > Usually major version upgrades introduce breaking changes. As far as I
> > > understood it, it just adds features. That would qualify for a second 
> > > digit
> > > increase.
> > > > >
> > > > > If we do a m

Some user guide errors

[Haonan Hou]

发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用


发件人: Haonan Hou
发送时间: Wednesday, October 9, 2019 10:08:09 AM
收件人: dev@iotdb.apache.org 
主题:

Hi all,

I found out lots of mistakes in the User Guide.

For example, in Chapter2 
Section1<https://iotdb.apache.org/#/Documents/0.8.0/chap2/sec1> page , there 
are links which are to Data Type and Encoding sections are invaild.
All most all links to another section are invaild. The reason is the Urls of 
there links include the wrong version numbers,
https://iotdb.apache.org/#/Documents/0.8.1/ .

Besides, another link error is in Chapter 4 Section 
7<https://iotdb.apache.org/#/Documents/0.8.0/chap4/sec7> .
At the bottom of this page, there is link about how to use IoTDB-JDBC is also 
invaild. The correct Url should be 
https://github.com/apache/incubator-iotdb/tree/master/example/jdbc/src/main/java/org/apache/iotdb.

Also, the version info in code shows v0.8.1, such as in 
https://iotdb.apache.org/#/Documents/0.8.0/chap7/sec1. The version should be 
0.8.0.

Best,
Haonan Hou

发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用

A bug of running mvnw.cmd in Windows OS

[Haonan Hou]

Hi,

I just tried to run `.\mvnw.cmd package -DskipTest` in windows 10 and got an 
error like this.
```
C:\Users\IoTDB\Documents\GitHub\incubator-iotdb>.\mvnw.cmd package -DskipTests
Couldn't find 
"C:\Users\IoTDB\Documents\GitHub\incubator-iotdb\.mvn\wrapper\maven-wrapper.jar",
 downloading it ...
Downloading from: 
"https://repo1.maven.org/maven2/io/takari/maven-wrapper/0.2.1/maven-wrapper-0.2.1.jar";
Finished downloading 
"C:\Users\IoTDB\Documents\GitHub\incubator-iotdb\.mvn\wrapper\maven-wrapper.jar"
Downloading 
https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.6.1/apache-maven-3.6.1-bin.zip

Exception in thread "main" javax.net.ssl.SSLException: 
java.lang.RuntimeException: Unexpected error: 
java.security.InvalidAlgorithmParameterException: the trustAnchors parameter 
must be non-empty
```

This bug may related to 
https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-254?filter=allopenissues.

I tried to replace the url from `https://` to `http://` and this problem didn’t 
appear again.

I am not sure if there is any other problem if I made this change.

Best,
Haonan Hou

Re: A bug of running mvnw.cmd in Windows OS

[Haonan Hou]

Hi Chris,

I am using OpenJDK 8 in my Windows machine. Let me try to install an Oracle JDK 
and see what happens.

Haonan

On Nov 12, 2019, at 4:41 PM, Christofer Dutz 
mailto:christofer.d...@c-ware.de>> wrote:

Hi Haonan,

what version of Java are you using?
I know that Java 7 had less available cypher suites available.

Chris



Am 12.11.19, 09:31 schrieb "Haonan Hou" 
mailto:hhao...@outlook.com>>:

   Hi,

   I just tried to run `.\mvnw.cmd package -DskipTest` in windows 10 and got an 
error like this.
   ```
   C:\Users\IoTDB\Documents\GitHub\incubator-iotdb>.\mvnw.cmd package 
-DskipTests
   Couldn't find 
"C:\Users\IoTDB\Documents\GitHub\incubator-iotdb\.mvn\wrapper\maven-wrapper.jar",
 downloading it ...
   Downloading from: 
"https://repo1.maven.org/maven2/io/takari/maven-wrapper/0.2.1/maven-wrapper-0.2.1.jar";
   Finished downloading 
"C:\Users\IoTDB\Documents\GitHub\incubator-iotdb\.mvn\wrapper\maven-wrapper.jar"
   Downloading 
https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.6.1/apache-maven-3.6.1-bin.zip

   Exception in thread "main" javax.net.ssl.SSLException: 
java.lang.RuntimeException: Unexpected error: 
java.security.InvalidAlgorithmParameterException: the trustAnchors parameter 
must be non-empty
   ```

   This bug may related to 
https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-254?filter=allopenissues.

   I tried to replace the url from `https://` to `http://` and this problem 
didn’t appear again.

   I am not sure if there is any other problem if I made this change.

   Best,
   Haonan Hou