Re: [VOTE] Apache IoTDB 1.3.0 RC1 release

[Gaofei Cao]

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, jdk17 [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);
select ** from root;

CREATE database root.sg1;
CREATE schema template t1 (s1 FLOAT encoding=RLE, s2 BOOLEAN
encoding=PLAIN compression=SNAPPY, s3 INT32);
SET SCHEMA TEMPLATE t1 to root.sg1;
INSERT INTO root.sg1.d1(timestamp,s1,s2,s3) values(1,1.1,false,1),
(2,2.2,false,2);
INSERT INTO root.sg1.d2(timestamp,s1,s2,s3) values(1,11.1,false,11),
(2,22.2,false,22);
INSERT INTO root.sg1.d3(timestamp,s1,s2,s3) values(1,111.1,true,null),
(4,444.4,true,44);
INSERT INTO root.sg1.d4(timestamp,s1,s2,s3)
values(1,.1,true,), (5,.5,false,);
INSERT INTO root.sg1.d4(timestamp,s1,s2,s3) values(2,22.2,true,22),
(3,333.3,false,333);

CREATE database root.sg2;
CREATE schema template t2 aligned (s1 FLOAT encoding=RLE, s2 BOOLEAN
encoding=PLAIN compression=SNAPPY, s3 INT32);
SET SCHEMA TEMPLATE t2 to root.sg2;
INSERT INTO root.sg2.d1(timestamp,s1,s2,s3) values(1,1.1,false,1),
(2,2.2,false,2);
INSERT INTO root.sg2.d2(timestamp,s1,s2,s3) values(1,11.1,false,11),
(2,22.2,false,22);
INSERT INTO root.sg2.d3(timestamp,s1,s2,s3) values(1,111.1,true,null),
(4,444.4,true,44);
INSERT INTO root.sg2.d4(timestamp,s1,s2,s3)
values(1,.1,true,), (5,.5,false,);
INSERT INTO root.sg2.d4(timestamp,s1,s2,s3) values(2,22.2,true,22),
(3,333.3,false,333);
INSERT INTO root.sg2.d5(timestamp,s1,s2,s3) values(2,22.2,true,22),
(3,333.3,false,333);
INSERT INTO root.sg2.d6(timestamp,s1,s2,s3) values(2,22.2,true,22),
(3,333.3,false,333);
INSERT INTO root.sg2.d4(timestamp,s1,s2,s3)
values(now(),22.2,true,22), (3,333.3,false,333);
INSERT INTO root.sg2.d5(timestamp,s1,s2,s3)
values(now(),22.2,true,22), (3,333.3,false,333);
INSERT INTO root.sg2.d6(timestamp,s1,s2,s3)
values(now(),22.2,true,22), (3,333.3,false,333);
INSERT INTO root.sg2.d7(timestamp,s1,s2,s3)
values(now(),22.2,true,22), (3,333.3,false,333);
SELECT * FROM root.sg1.** where time > 1 and time < 5 and s3>=11 and
s3<= and s1 != 11.1 ORDER BY TIME DESC ALIGN BY DEVICE;
SELECT * FROM root.sg2.** where time > 1 and time < 5 and s3>=11 and
s3<= and s1 != 11.1 ORDER BY TIME DESC ALIGN BY DEVICE;
SELECT s3,s2 FROM root.sg1.** where time > 1 and time < 5 and s3>=11
and s3<= and s1 != 11.1 ORDER BY TIME DESC ALIGN BY DEVICE;
SELECT s3,s2 FROM root.sg2.** where time > 1 and time < 5 and s3>=11
and s3<= and s1 != 11.1 ORDER BY TIME DESC ALIGN BY DEVICE;
```

Best,
—
Gaofei Cao

Haonan Hou  于2023年12月27日周三 12:34写道：
>
> 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

Re: Add -XX:+ExitOnOutOfMemoryError as default JVM parameter in datanode-env and confignode-env

[Gaofei Cao]

+1,

 `-XX:+ExitOnOutOfMemoryError` parameter can avoid the loss of some
key threads, it will be beneficial to the system.
If the IoTDB cluster is deployed on k8s, this parameter is more
indispensable, because k8s can dispatch another pod to replace this
OOM node rapidly.
Besides, i think we can add the usage of `-XX:+ExitOnOutOfMemoryError`
and `-XX:+HeapDumpOnOutOfMemoryError` in the user/DBA manual, which is
important to find the root cause of OOM.

Best,
--
Gaofei Cao

Yuan Tian  于2023年11月13日周一 19:52写道：
>
> Hi all,
>
> Recently, we found in some real user cases that when OOM occurs in the
> DataNode process (although we should ensure that OOM does not happen, but
> we all know that bugs will always exist), some threads(e.g. rpc listening
> threads) may exit unexpectedly which may cause some strange things to
> happen. For example, if the heartbeat listening thread on the DataNode
> unexpectedly exits due to OOM, and then the OOM recovers on its own (some
> large queries end, or some compaction tasks end), but this thread will
> never exist again, causing the DataNode to remain in unknown state, because
> the ConfigNode can no longer contact it via heartbeat.
>
> Therefore, we feel that OOM is a high-risk error, and we should let the
> process exit directly to avoid the loss of some key threads.
>
> And I did an experiment and found that -XX:+ExitOnOutOfMemoryError and
> -XX:+HeapDumpOnOutOfMemoryError do not conflict which means that we can
> keep both in jvm args and when OOM happens, it will firstly dump the heap
> memory and then exit.
>
> I've made this change in my pr(https://github.com/apache/iotdb/pull/11531).
>
> What do you think?
>
>
>
>
> Best,
> --
> Yuan Tian

Re: Rollcall TsFile initial committers

[Gaofei Cao]

Hi Jialin,

I would like to be the initial committer of TsFile.
I participated in the design and development of the first version of
TsFile, familiar with the query process, file structure and other
system integrations.
And now I'm participating in the work to push down value filter. I
wish I could bring more features to make TsFile a better file format.


Thanks

Gaofei Cao

Haonan Hou  于2023年10月17日周二 14:39写道：
>
>
> 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: [VOTE] Apache IoTDB 1.2.2 RC1 release

[Gaofei Cao]

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, jdk17 [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);
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);
show timeseries;
select ** from root.**;



Best,
-
Gaofei Cao

Jialin Qiao  于2023年10月12日周四 21:28写道：
>
> 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);
> select ** from root;
> select ** from root align by device;
>
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC
>
> Yuan Tian  于2023年10月12日周四 20: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

Re: [VOTE] Apache IoTDB 1.2.1 RC1 release

[Gaofei Cao]

Hi,

+1 (binding), v1.2.1 has also been verified by Benchant.

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, ubuntu, jdk17 [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);
select ** from root;

Best,
—
Gaofei Cao

Gaofei Cao  于2023年9月18日周一 17:24写道：
>
> Hi, +1 (binding)
>
> Jialin Qiao  于2023年9月16日周六 10:42写道：
> >
> > 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);
> > select ** from root;
> >
> > Thanks,
> > —
> > Jialin Qiao
> > Apache IoTDB PMC
> >
> > Yuan Tian  于2023年9月15日周五 18:14写道：
> > >
> > > 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

Re: [VOTE] Apache IoTDB 1.2.1 RC1 release

[Gaofei Cao]

Hi, +1 (binding)

Jialin Qiao  于2023年9月16日周六 10:42写道：
>
> 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);
> select ** from root;
>
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC
>
> Yuan Tian  于2023年9月15日周五 18:14写道：
> >
> > 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

Re: [VOTE] Apache IoTDB 1.2.0 RC2 release

[Gaofei Cao]

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, jdk17 [ok]
statements executed successfully:  [ok]

SET STORAGE GROUP TO root.turbine;
CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE, ENCODING=RLE;
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,

Gaofei Cao

Re: Move Jenkins notifications to another list

[Gaofei Cao]

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 
> .
>
> Any idea?
>
> Best,
> Haonan Hou

Re: [VOTE] Apache IoTDB 1.1.2 RC1 release

[Gaofei Cao]

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, jdk17 [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;
select count(*) from root.sg.**;


---
Thanks,
Gaofei Cao

Refactor the package structure of IoTDB

[Gaofei Cao]

Hi All,

To make the the package structure of IoTDB more concise and tidy, we
have moved the package `antlr`, `confignode`, `consensus`, `metrics`,
`mlnode`, 'node-commons' and `server` to a new package `iotdb-core`.

The package structure before changed:
Parent
├──antrl
├──confignode
├──consensus
├──iotdb-api
├──iotdb-client
├──iotdb-connector
├──iotdb-protocol
├──library-udf
├──metrics
├──mlnode
├──node-commons
├──server
├──tsfile


The package structure after changed (master branch):
Parent
├── iotdb-api
├── iotdb-client
├── iotdb-connector
├── iotdb-core
  └── antlr
  └── confignode
  └── consensus
  └── datanode (sever package before changed)
  └── metrics
  └── mlnode
  └── node-commons
  └── tsfile
├── iotdb-protocol
├── library-udf


Thanks.

Gaofei Cao
Apache IoTDB PMC

Re: Re: [VOTE] Apache IoTDB 1.1.0 RC2 release

[Gaofei Cao]

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, jdk-11 [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.**;

Best,
—
Gaofei Cao
Apache IoTDB PMC

张金瑞 <329920...@qq.com.invalid> 于2023年4月1日周六 17:27写道：
>
> 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, jdk-11 [ok]
> statements executed successfully: [ok]
>
> insert into root.test.d1(time,s1) values(168034108,1);
> insert into root.test.d1(time,s1) values(1680341081000,2);
> insert into root.test.d1(time,s1) values(1680341082000,3);
> select * from root.test.**;
>
> Thanks,
> Jinrui Zhang
> Apache IoTDB PMC
>
>
>
>
>
>
>
>
> Original
>
>
>
> From:"Jialin Qiao"< qiaojia...@apache.org ;
>
> Date:2023/4/1 16:09
>
> To:"dev"< dev@iotdb.apache.org ;
>
> Subject:Re: [VOTE] Apache IoTDB 1.1.0 RC2 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, 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.**;
>
> Best,
> —
> Jialin Qiao
> Apache IoTDB PMC
>
> Haonan Hou  于2023年3月31日周五 11:44写道：
> 
>  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

[ANNOUNCE] Apache IoTDB 1.0.1 released

[Gaofei Cao]

The Apache IoTDB team is pleased to announce the release of Apache IoTDB
1.0.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.

This is a bug-fixed version of 1.0.0, which includes a number of new
features and improvements:

## New Features

* [IOTDB-5102] Support explain the sqls using align by device clause
* [IOTDB-5282] Add SQL show variables, which can display the current
cluster variables

## Improvements

* [IOTDB-4595] Add real-time monitoring data for tsfile merge
* [IOTDB-5125] Stop the process when port is already in use when
launching ConfigNode or DataNode
* [IOTDB-5185] Fixed that old snapshot is not deleted in IoTConsensus
* [IOTDB-5202] Support showing regions regarding database
* [IOTDB-5205] Construct Cluster Node startup protocol, reject start
or restart request of ConfigNode or DataNode when using wrong data
* [IOTDB-5208] Fix increase of file handles when TsFileResource is
degraded and compacted with fast performer
* [IOTDB-5223] Cause DataNode startup to fail when multiple disks are
configured in the data directory and the dataRegion consensus protocol
uses Ratis
* [IOTDB-5232] Add Schema Memory Usage metric monitor
* [IOTDB-5249] Add interface to set datatype when users customize the
payload formatter of mqtt
* [IOTDB-5258] Add timeout parameter for ExportCSV/ExportTsFile Tool
* [IOTDB-5306] Change the default port of ConfigNode and DataNode
* [IOTDB-5326] Add cluster_name parameter to distinguish different cluster
* [IOTDB-5389] Cause DataNode starup to fail when wal_mode is disabled
in IoTConsensus

## Bug Fixes

* [IOTDB-4978] Fix possible deadLock while using select into
* [IOTDB-5090] Fix the NPE when executing stop-datanode.sh
* [IOTDB-5116] Fix wrong empty result set in aggregation query while
there is no data in queried timeseries
* [IOTDB-5118] Fix that datanode opens too many file handles （TYPE DIR）
* [IOTDB-5174] Fixed restart failure when IoTConsensus hostname containing '-'
* [IOTDB-5126] Fix that show-regions show IP rather than hostname even
though the hostname is used when registering
* [IOTDB-5135] Fix the Sync snapshot failure (also blocks ConfigNode
snapshot) when sync file is empty
* [IOTDB-5141] Fix fast compaction scheduler bug
* [IOTDB-5144] Fix classCastException in IoTDBDatabaseMetadata of jdbc
* [IOTDB-5158] Fix failure of getting devices from tsfile
* [IOTDB-5170] Fix the problem that datanode is closed when executing
stop-confignode.bat on Windows platform
* [IOTDB-5210] Fix concurrent bug caused by init and close of driver
* [IOTDB-5212] Upgrade an illegal CQ verification prompt from v0.14.0 to v1.0
* [IOTDB-5215] Fix the wrong usage of chunkPointNumLowerBound in IoTDBDescriptor
* [IOTDB-5216] Fix order by timeseries doesn't take effect in aligned last query
* [IOTDB-5222] Fix the load of some metric related configuration
* [IOTDB-5231] Fix that Datanode could not start when binding 9091 error
* [IOTDB-5233] Correct the message of unsupported thrift interface of
schema template
* [IOTDB-5236] Fix DeleteData Python API cannot work
* [IOTDB-5240] Fix schema template timeseries read/write error after restart
* [IOTDB-5261] Fix the number of clients in client pool of
AsyncIoTConsensusServiceClient can not be changed through
dn_max_connection_for_internal_service
* [IOTDB-5266] Refine the code of cross selector and fix the bug when
using FileTImeIndex
* [IOTDB-5269] Fix wrong data of devices ought to be deleted after
executing `delete from` sql
* [IOTDB-5277] Fix DataNode restart failure when SchemaRegion loading snapshot
* [IOTDB-5278] Fix JDBC Driver cannot connect to the dbeaver
* [IOTDB-5285] Fix TimePartition error when restarting with different
time partition configuration
* [IOTDB-5286] Fix target files are selected to participate in other
compaction task
* [IOTDB-5313] Fix Python client doesn't handle REDIRECTION_RECOMMEND correctly
* [IOTDB-5452] Add leastDataRegionGroupNumSetByUser examination to
ensure that leastDataRegionGroupNum will not be changed by system
* [IOTDB-5498] Fix SessionPool OOM problem when the number of devices
and sessions is large
* [IOTDB-5501] Fix memory leak in MemoryPool
* [IOTDB-5525] Fix the partition error of device after partition fetcher

The full release note is available at:
https://raw.githubusercontent.com/apache/iotdb/v1.0.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=g:org.apache.iotdb


Regards,
The Apache IoTDB team

[RESULT][VOTE] Release Apache IoTDB 1.0.1

[Gaofei Cao]

Hi all,


The vote to release Apache IoTDB 1.0.1 has passed with 3 +1 binding votes.

binding votes:

Jialin Qiao

Jinrui Zhang

Haonan Hou


Vote thread:

https://lists.apache.org/thread/8204q67yv11dnb7mwdh65cv9fkjzmown
https://lists.apache.org/thread/zjg6rkogohmykmmmj8bd13jntd5t564s
https://lists.apache.org/thread/wcdp97dr353tov8tk8dp9jz4tk2cp0kw

Thanks,
Gaofei Cao

[VOTE] Apache IoTDB 1.0.1 RC1 release

[Gaofei Cao]

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: new committer: Haiming Zhu

[Gaofei Cao]

Congratulations! Haiming made a great contributions for WAL and IoTConsensus !


Gaofei Cao

Houliang Qi  于2023年1月5日周四 14:37写道：


>
> Congratulations! Haiming made a great work for WAL.
>
>
> Thanks,
> ---
> Houliang Qi
> BONC, Ltd
>
>
>  Replied Message 
> | From | 谭新宇<1025599...@qq.com.INVALID> |
> | Date | 01/5/2023 10:09 |
> | To |  |
> | Subject | Re: new committer: Haiming Zhu |
> Congratulations Haiming!
>
> 
> Xinyu Tan
>
> 2022年12月28日 23:31，Jialin Qiao  写道：
>
> Hi,
>
> The Project Management Committee (PMC) for Apache IoTDB
> has invited Haiming Zhu to become a committer and we are pleased
> to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> You could get the write-access of our repository by:
>
> (1) Update your github id in: id.apache.org , also an email (anything
> to your apache email will forward to this email).
> (2) Accept the invitation in github to be a member of the apache group.
> (3) Link your accounts via: git.apache.org (To lighten the third
> option MFA Status, you need to download Google Authenticator (Google
> 身份验证器) in your mobile)
> (4）Sign in github by Google Authenticator
> (5) Clone repository with ssh.
>
> Welcome, Haiming!
>
> Yours,
> The Apache IoTDB PMC

Re: new committer: Rongzhao Chen

[Gaofei Cao]

Congratulations Rongzhao!


Gaofei Cao

谭新宇 <1025599...@qq.com.invalid> 于2023年1月5日周四 11:01写道：
>
> Congratulations rongzhao!
>
> 
> Xinyu Tan
>
> > 2023年1月4日 17:46，HW-Chao Wang <576749...@qq.com.INVALID> 写道：
> >
> > Congratulations, Rongzhao has made outstanding contributions to the 
> > confignode architecture and code
> >
> >
> >
> > ---Original---
> > From: "Jialin Qiao" > Date: Wed, Jan 4, 2023 17:10 PM
> > To: "dev" > Subject: new committer: Rongzhao Chen
> >
> >
> > Hi,
> >
> > The Project Management Committee (PMC) for Apache IoTDB
> > has invited Rongzhao Chen to become a committer and we are pleased
> > to announce that he has accepted.
> >
> > Being a committer enables easier contribution to the
> > project since there is no need to go via the patch
> > submission process. This should enable better productivity.
> >
> > You could get the write-access of our repository by:
> >
> > (1) Update your github id in: id.apache.org , also an email (anything
> > to your apache email will forward to this email).
> > (2) Accept the invitation in github to be a member of the apache group.
> > (3) Link your accounts via: git.apache.org (To lighten the third
> > option MFA Status, you need to download Google Authenticator (Google
> > 身份验证器) in your mobile)
> > (4）Sign in github by Google Authenticator
> > (5) Clone repository with ssh.
> >
> > Welcome, Yongzao!
> >
> > Yours,
> > The Apache IoTDB PMC
>

Re: Change the default port of ConfigNode and DataNode

[Gaofei Cao]

dn_rpc_port, 6667 => 6667
dn_internal_port, 9003 => 10710
dn_mpp_data_exchange_port, 8777 => 10720
dn_schema_region_consensus_port, 50010 => 10730
dn_data_region_consensus_port, 40010 => 10740
cn_internal_port, 22277 => 10750
cn_consensus_port, 22278 => 10760

Thanks,
-----------
Gaofei Cao

Gaofei Cao  于2022年12月20日周二 10:35写道：
>
> The original port of `dn_schema_region_consensus_port` in DataNode is
> 50010, which may be conflict with HDFS system.
>
> And the original used ports are 6667、9003、8777、50010、40010、22277 and
> 22278, which are not in a regular range, so we want to change the
> default used ports as the picture below.
>
> What do your opinion about the port changes?
>
>
> Thanks,
> ---
> Gaofei Cao

Change the default port of ConfigNode and DataNode

[Gaofei Cao]

The original port of `dn_schema_region_consensus_port` in DataNode is
50010, which may be conflict with HDFS system.

And the original used ports are 6667、9003、8777、50010、40010、22277 and
22278, which are not in a regular range, so we want to change the
default used ports as the picture below.

What do your opinion about the port changes?


Thanks,
---
Gaofei Cao

Re: [VOTE] Apache IoTDB 1.0.0 RC5 release

[Gaofei Cao]

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


The binary distribution:
the version number in CLI [ok]
signatures and hashes [ok]
start in mac, jdk11 [ok]
statements executed successfully:  [ok]
start-standalone.sh 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;

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

Thanks,

Gaofei Cao

勇敢的心  于2022年12月4日周日 22:25写道：
>
> +1
>
>
>
> Guanfei Guo
> guoguan...@qq.com
>
>
> 
>
>
>
>
> --Original--
> From: 
>"dev"  
>   
>  Date:Fri, Dec 2, 2022 07:22 PM
> To:"dev"
> Subject:Re: [VOTE] Apache IoTDB 1.0.0 RC5 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
>
>
> The binary distribution:
> the version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk11 [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,
> 
> Yuan Tian
>
>
> On Fri, Dec 2, 2022 at 5:22 PM 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: 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

Re: [VOTE] Apache IoTDB 1.0.0 RC3 release

[Gaofei Cao]

-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

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

[Gaofei Cao]

+1

Thanks,
—
Gaofei Cao
Apache IoTDB PMC

CloudWise-Luke <282583...@qq.com.invalid> 于2022年11月7日周一 11:12写道：
>
> +1
>
>
>
> CloudWiseluke.miao
>
>
> 
>
>
>
>
> --原始邮件--
> 发件人:  
>   "dev"   
>  
>  发送时间:2022年11月7日(星期一) 上午10:00
> 收件人:"dev"
> 主题:[VOTE] Create a repo for TsFile-Viewer
>
>
>
> 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: Renaming partition region to config node

[Gaofei Cao]

+1


Thanks,
—
Gaofei Cao
Apache IoTDB PMC

HW-Chao Wang <576749...@qq.com.invalid> 于2022年11月4日周五 19:33写道：

>
> +1
>
>
>
> ---Original---
> From: "Jialin Qiao" Date: Fri, Nov 4, 2022 19:28 PM
> To: "dev" Subject: Renaming partition region to config node
>
>
> Hi,
>
> Currently, we have some parameters like
> partition_region_consensus_protocol_class, which actually specify the
> consensus class of the config node.
>
> Therefore, defining an abstract partition region is unnecessary, we'd
> better rename it as config_node_consensus_protocol_class directly for
> better comprehension.
>
> Besides, I adjust some parameters' locations for convenience.
>
> https://github.com/apache/iotdb/pull/7909
>
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC

Re: Chaneg the name of StandAloneConsensus

[Gaofei Cao]

+1 for SimpleConsensus

OneCopy may be ambiguous. SimpleConsensus naming is friendly for new user.

Thanks,
Gaofei Cao

Jialin Qiao  于2022年11月2日周三 16:08写道：
>
> +1 for SimpleConsensus
>
> OneCopy may cause confuse, Users may treat one replica as OneCopy.
>
> Or treat OneCopy as two replicas ( one primary + one copy)
>
> Thanks,
> Jialin Qiao
>
>
> On 2022/11/02 04:14:52 Haonan Hou wrote:
> > +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] Apache IoTDB 0.13.3 release

[Gaofei Cao]

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

These two files are generated when compiling the source code, we should
omit them.

The binary distribution:
the version number in CLI [ok]
signatures and hashes [ok]
start in mac, jdk11 [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,
Gaofei Cao

Yuan Tian  于2022年10月20日周四 11:26写道：
>
> 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
>
>
> These two files are generated when compiling the source code, we should
> omit them.
>
> The binary distribution:
> the version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk11 [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,
> 
> Yuan Tian
>
> On Mon, Oct 17, 2022 at 9:31 PM Jialin Qiao  wrote:
> >
> > Hi all,
> >
> > Apache IoTDB 0.13.3 is a bug-fix version from 0.13.2. You can get its
> > mainly changes from [5].
> >
> > Apache IoTDB 0.13.3 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: v0.13.3
> > Hash for the release tag: c3b9955e4b057b92c586baea68904458d48596fc
> >
> > 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-1088
> > [2] https://dist.apache.org/repos/dist/dev/iotdb/0.13.3/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/0.13.3/rc1/RELEASE_NOTES.md
> > [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> >
> > Best,
> >
> > Jialin Qiao
> > Apache IoTDB PMC

Re: [VOTE] Apache IoTDB 0.14.0-preview2 RC2 release

[Gaofei Cao]

, FALSE);
insert into root.sg1.d1(time, s3, s4) aligned values(30, 30, FALSE);
insert into root.sg1.d2(time, s3, s4) values(21, 21, TRUE);
insert into root.sg1.d2(time, s3, s4) values(22, 22, TRUE);
insert into root.sg1.d2(time, s3, s4) values(23, 23, TRUE);
insert into root.sg1.d2(time, s3, s4) values(24, 24, TRUE);
insert into root.sg1.d2(time, s3, s4) values(25, 25, TRUE);
insert into root.sg1.d2(time, s3, s4) values(26, 26, FALSE);
insert into root.sg1.d2(time, s3, s4) values(27, 27, FALSE);
insert into root.sg1.d2(time, s3, s4) values(28, 28, FALSE);
insert into root.sg1.d2(time, s3, s4) values(29, 29, FALSE);
insert into root.sg1.d2(time, s3, s4) values(30, 30, FALSE);
flush;
insert into root.sg1.d1(time, s1, s3, s4) aligned values(23, 23.0,
23, FALSE);
insert into root.sg1.d1(time, s2, s5) aligned values(31, 31, 'aligned_test31');
insert into root.sg1.d1(time, s2, s5) aligned values(32, 32, 'aligned_test32');
insert into root.sg1.d1(time, s2, s5) aligned values(33, 33, 'aligned_test33');
insert into root.sg1.d1(time, s2, s5) aligned values(34, 34, 'aligned_test34');
insert into root.sg1.d1(time, s2, s5) aligned values(35, 35, 'aligned_test35');
insert into root.sg1.d1(time, s2, s5) aligned values(36, 36, 'aligned_test36');
insert into root.sg1.d1(time, s2, s5) aligned values(37, 37, 'aligned_test37');
insert into root.sg1.d1(time, s2, s5) aligned values(38, 38, 'aligned_test38');
insert into root.sg1.d1(time, s2, s5) aligned values(39, 39, 'aligned_test39');
insert into root.sg1.d1(time, s2, s5) aligned values(40, 40, 'aligned_test40');
insert into root.sg1.d2(time, s2, s5) values(31, 31, 'non_aligned_test31');
insert into root.sg1.d2(time, s2, s5) values(32, 32, 'non_aligned_test32');
insert into root.sg1.d2(time, s2, s5) values(33, 33, 'non_aligned_test33');
insert into root.sg1.d2(time, s2, s5) values(34, 34, 'non_aligned_test34');
insert into root.sg1.d2(time, s2, s5) values(35, 35, 'non_aligned_test35');
insert into root.sg1.d2(time, s2, s5) values(36, 36, 'non_aligned_test36');
insert into root.sg1.d2(time, s2, s5) values(37, 37, 'non_aligned_test37');
insert into root.sg1.d2(time, s2, s5) values(38, 38, 'non_aligned_test38');
insert into root.sg1.d2(time, s2, s5) values(39, 39, 'non_aligned_test39');
insert into root.sg1.d2(time, s2, s5) values(40, 40, 'non_aligned_test40');

select ** from root;
select last ** from root.sg1.*;
select ** from root.sg1.d1 where time >= 9 and time <= 33 and s1 < 19
align by device;
select max_value(s3), min_value(s1), max_time(s2), min_time(s3) from
root.sg1.d1 where time > 5 GROUP BY ([1, 41), 10ms) order by time
desc;

Thanks,
—————————
Gaofei Cao
Apache IoTDB PMC

Jialin Qiao  于2022年9月8日周四 17:46写道：
>
> 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 clean install -DskipTests  [ok]
>
>
> The binary distribution:
> version number in CLI [ok]
> signatures and hashes [ok]
> 3C3D start in mac, jdk8 [ok]
> Insert and query statements executed successfully:  [ok]
>
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC
>
> Yuan Tian  于2022年9月8日周四 09:40写道：
> >
> > 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  [minor issue with
> > a target file not ignored by apache-rat]
> >
> >
> > The binary distribution:
> > version number in CLI [ok]
> > signatures and hashes [ok]
> > start in mac M1 pro, jdk11-liberica [ok]
> > statements executed successfully:  [ok]
> >
> > SET STORAGE GROUP TO root.sg1;
> > create aligned timeseries root.sg1.d1(s1 FLOAT encoding=RLE, s2 INT32
> > encoding=Gorilla compression=SNAPPY, s3 INT64, s4 BOOLEAN, s5 TEXT);
> > create timeseries root.sg1.d2.s1 WITH DATATYPE=FLOAT, encoding=RLE;
> > create timeseries root.sg1.d2.s2 WITH DATATYPE=INT32, encoding=Gorilla;
> > create timeseries root.sg1.d2.s3 WITH DATATYPE=INT64;
> > create timeseries root.sg1.d2.s4 WITH DATATYPE=BOOLEAN;
> > create timeseries root.sg1.d2.s5 WITH DATATYPE=TEXT;
> > insert into root.sg1.d1(time, s1, s2, s3, s4, s5) aligned values(1,
> > 1.0, 1, 1, TRUE, 'aligned_test1');
> > insert into root.sg1.d1(time, s1, s2, s3, s5) aligned values(2, 2.0,
> > 2, 2, 'aligned_test2');
> > insert into root.sg1.d1(time, s1, s3, s4, s5) aligned values(3, 3.0,
> > 3, FALSE, 'aligned_test3');
> > insert into root.sg1.d1(time, s1, s2, s4, s5) aligned values(4, 4.0,
> > 4, TRUE, 'aligned_test4');
> > insert into root.sg1.d1(time, s1, s2, s4, s5) aligned values(5, 5.0,
> 

Re: [VOTE] Apache IoTDB 0.13.2 RC1 release

[Gaofei Cao]

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

The binary distribution:
the 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,
Gaofei Cao

Haonan Hou  于2022年9月5日周一 09:55写道：
>
> 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
>
> The binary distribution:
> the version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk11 [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,
> Haonan Hou
>
> > On Sep 1, 2022, at 10:27 PM, Jialin Qiao  wrote:
> >
> > Hi all,
> >
> > Apache IoTDB 0.13.2 is a bug-fix version from 0.13.1. You can get its main
> > changes from [5].
> >
> > Apache IoTDB 0.13.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: v0.13.2
> > Hash for the release tag: 1188ee17e6fd7afaab4e92b2e20c32f738d46fb3
> >
> > 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-1085
> > [2] https://dist.apache.org/repos/dist/dev/iotdb/0.13.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://dist.apache.org/repos/dist/dev/iotdb/0.13.2/rc1/RELEASE_NOTES.md
> > [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> >
> > Best,
> >
> > Jialin Qiao
> >
>

Re: Apply to join IotDB

[Gaofei Cao]

Welcome!
—
Gaofei Cao
Apache IoTDB PMC

Jialin Qiao  于2022年8月16日周二 16:02写道：

>
> Welcome! Added to Jira.
> —
> Jialin Qiao
> Apache IoTDB PMC
>
>
> 曹志佳  于2022年8月16日周二 14:11写道：
>
> > Hi, I'm Cao Zhijia,from Timecho!
> >
> >
> > Confluence id:Zhijia Cao
> > Jira id:caozhijia1

Re: [VOTE] Apache IoTDB 0.13.1 RC1 release

[Gaofei Cao]

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


These two files are generated when compiling the source code, we should
omit them.

The binary distribution:
the 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,
Gaofei Cao

冯 庆新  于2022年8月3日周三 16:19写道：
>
> -1
> I think you hava to prepare release RC2,because “[To rel/0.13][IOTDB-2736] 
> DELETE_STORAGE_GROUP can not be granted to user (reporting 401)” maybe a 
> criticlt issue too.
>
>
> 发件人: Haonan Hou<mailto:hhaonan4...@qq.com.INVALID>
> 发送时间: 2022年8月3日 9:30
> 收件人: dev-iotdb<mailto:dev@iotdb.apache.org>
> 主题: Re: [VOTE] Apache IoTDB 0.13.1 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
>
>
> These two files are generated when compiling the source code, we should
> omit them.
>
> The binary distribution:
> the version number in CLI [ok]
> signatures and hashes [ok]
> start in mac, jdk11 [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,
> Haonan Hou
>
> > On Aug 3, 2022, at 9:14 AM, Yuan Tian  wrote:
> >
> > Hi,
> >
> > +1(binding)
> >
> > Best,
> > -
> > Yuan Tian
> >
> > On Mon, Aug 1, 2022 at 10:18 AM Jialin Qiao  wrote:
> >>
> >> Hi all,
> >>
> >> Apache IoTDB 0.13.1 is a bug-fix version from 0.13.0. You can get its
> >> mainly changes from [5].
> >>
> >> Apache IoTDB v0.13.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: v0.13.1
> >> Hash for the release tag: 8dd7aa670bf4ceabf8dd27dd9817de8cd0669e82
> >>
> >> 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-1081/
> >> [2] https://dist.apache.org/repos/dist/dev/iotdb/0.13.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/0.13.1/rc1/RELEASE_NOTES.md
> >> [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> >>
> >>
> >> Best,
> >> -
> >> Jialin Qiao
> >> Apache IoTDB PMC
>

Re: [VOTE] Apache IoTDB 0.12.6 RC1 release

[Gaofei Cao]

Hi, +1 (binding)

I checked these on my Mac (Apple M1 Pro), JDK 1.8

The source release:
LICENSE and NOTICE [ok]
signatures and hashes [ok]
could compile from source: mvn clean install [not ok], some generated
py files should be ignored by rat checker

The binary distribution:
signatures and hashes [ok]
start server and CLI in mac, jdk1.8 [ok]
Could run with the following statements [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;


Gaofei Cao
Apache IoTDB PMC

>
> Hi,
>
> +1 (binding)
>
> I checked these on my Mac, JDK 8 and 11
>
> The source release:
> LICENSE and NOTICE [ok]
> signatures and hashes [ok]
> could compile from source: mvn clean install [not ok]
> some generated py files should be ignored by rat checker
>
> The binary distribution:
> signatures and hashes [ok]
> start server and CLI in mac, jdk8 and jdk11 [ok]
> Could run with the following statements [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,
>
> Haonan Hou
>
> > On Jul 12, 2022, at 2:21 PM, BensonChou <2027178...@qq.com.INVALID> wrote:
> >
> > +1
> >
> >
> >
> > ---Original---
> > From: "Yuan Tian" > Date: Fri, Jul 8, 2022 18:08 PM
> > To: "dev" > Subject: [VOTE] Apache IoTDB 0.12.6 RC1 release
> >
> >
> > Hi all,
> >
> > Apache IoTDB 0.12.6 is a bug-fix version from 0.12.5. You can get its
> > mainly changes from [5].
> >
> > Apache IoTDB 0.12.6 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: v0.12.6
> > Hash for the release tag: eeb67fab595e090bfc67c62f45017d618acd24cf
> >
> > 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-1079
> > [2] https://dist.apache.org/repos/dist/dev/iotdb/0.12.6/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/0.12.6/rc1/RELEASE_NOTES.md
> > [6] https://dist.apache.org/repos/dist/dev/iotdb/KEYS
> >
> >
> > Best,
> > -
> > Yuan Tian
>

Re: [VOTE] Apache IoTDB 0.14.0-preview1 RC1 release

[Gaofei Cao]

 into root.sg1.d1(time, s3, s4) aligned values(29, 29, FALSE);
insert into root.sg1.d1(time, s3, s4) aligned values(30, 30, FALSE);
insert into root.sg1.d2(time, s3, s4) values(21, 21, TRUE);
insert into root.sg1.d2(time, s3, s4) values(22, 22, TRUE);
insert into root.sg1.d2(time, s3, s4) values(23, 23, TRUE);
insert into root.sg1.d2(time, s3, s4) values(24, 24, TRUE);
insert into root.sg1.d2(time, s3, s4) values(25, 25, TRUE);
insert into root.sg1.d2(time, s3, s4) values(26, 26, FALSE);
insert into root.sg1.d2(time, s3, s4) values(27, 27, FALSE);
insert into root.sg1.d2(time, s3, s4) values(28, 28, FALSE);
insert into root.sg1.d2(time, s3, s4) values(29, 29, FALSE);
insert into root.sg1.d2(time, s3, s4) values(30, 30, FALSE);
flush;
insert into root.sg1.d1(time, s1, s3, s4) aligned values(23, 23.0,
23, FALSE);
insert into root.sg1.d1(time, s2, s5) aligned values(31, 31, 'aligned_test31');
insert into root.sg1.d1(time, s2, s5) aligned values(32, 32, 'aligned_test32');
insert into root.sg1.d1(time, s2, s5) aligned values(33, 33, 'aligned_test33');
insert into root.sg1.d1(time, s2, s5) aligned values(34, 34, 'aligned_test34');
insert into root.sg1.d1(time, s2, s5) aligned values(35, 35, 'aligned_test35');
insert into root.sg1.d1(time, s2, s5) aligned values(36, 36, 'aligned_test36');
insert into root.sg1.d1(time, s2, s5) aligned values(37, 37, 'aligned_test37');
insert into root.sg1.d1(time, s2, s5) aligned values(38, 38, 'aligned_test38');
insert into root.sg1.d1(time, s2, s5) aligned values(39, 39, 'aligned_test39');
insert into root.sg1.d1(time, s2, s5) aligned values(40, 40, 'aligned_test40');
insert into root.sg1.d2(time, s2, s5) values(31, 31, 'non_aligned_test31');
insert into root.sg1.d2(time, s2, s5) values(32, 32, 'non_aligned_test32');
insert into root.sg1.d2(time, s2, s5) values(33, 33, 'non_aligned_test33');
insert into root.sg1.d2(time, s2, s5) values(34, 34, 'non_aligned_test34');
insert into root.sg1.d2(time, s2, s5) values(35, 35, 'non_aligned_test35');
insert into root.sg1.d2(time, s2, s5) values(36, 36, 'non_aligned_test36');
insert into root.sg1.d2(time, s2, s5) values(37, 37, 'non_aligned_test37');
insert into root.sg1.d2(time, s2, s5) values(38, 38, 'non_aligned_test38');
insert into root.sg1.d2(time, s2, s5) values(39, 39, 'non_aligned_test39');
insert into root.sg1.d2(time, s2, s5) values(40, 40, 'non_aligned_test40');

select * from root;
select last * from root.sg1.*;
select * from root.sg1.d1 where time >= 9 and time <= 33 and s1 < 19
align by device;
select max_value(s3), min_value(s1), max_time(s2), min_time(s3) from
root.sg1.d1 where time > 5 GROUP BY ([1, 41), 10ms) order by time
desc;


Best,
————

Gaofei Cao
Apache IoTDB PMC

Re: Change rpc_address to internal_address in ConfigNode and refactor show cluster

[Gaofei Cao]

Agreed with it.
The changing of 'rpc_address' and 'rpc_port' for ConfigNodes is reasonable.

But if we provide rpc service for ConfigNode in the future, the
rpc_address for ConfigNode may be re-enabled again.

冯 庆新  于2022年6月30日周四 11:40写道：
>
> +1
>
> 发件人: Yuan Tian
> 发送时间: 2022年6月30日 11:23
> 收件人: dev
> 主题: Re: Change rpc_address to internal_address in ConfigNode and refactor 
> show cluster
>
> +1
>
> Best,
> -
> Yuan Tian
>
> On Thu, Jun 30, 2022 at 9:45 AM Jialin Qiao  wrote:
> >
> > Hi,
> >
> > As ConfigNode only serve DataNodes and other ConfigNode.
> >
> > The rpc_address in ConfigNode should be internal_address.
> > The rpc_port in ConfigNode should be internal_port.
> >
> > After this, the show cluster function needs to be refactored.
> >
> > Previously, show cluster print the rpc_address of DataNode and ConfigNode,
> > however, rpc_address for DataNode is the client_rpc_service.
> >
> > So it's better to print the internal_address of DataNode and ConfigNode.
> >
> > What do you think?
> >
> > Thanks,
> > —
> > Jialin Qiao
> > Apache IoTDB PMC
>

Re: [VOTE] Charta and proposal for first VP

[Gaofei Cao]

Hi, big +1.

Best,
--
Gaofei Cao

Houliang Qi  于2020年9月3日周四 下午8:50写道：

>
> Hi,
> big +1.
>
>
>
>
> Thanks,
> ---
> Houliang Qi
>
>
> On 09/3/2020 20:47，runhus...@foxmail.com wrote：
> Hi，
> big +1.
>
>
>
> Thanks.
>
> Chao Wang
> BONC Ltd
>
>
> From: Xiangwei Wei
> Date: 2020-09-03 20:17
> To: dev
> Subject: Re: [VOTE] Charta and proposal for first VP
> Hi,
>
> big +1.
>
> Jack Tsai  于2020年9月3日周四 下午7:54写道：
>
> Hi,
>
> +1
>
> Best,
>
> Tsung-Han (Jack) Tsai
>
> 
> From: Jialin Qiao 
> Sent: Thursday, September 3, 2020 7:25 PM
> To: dev@iotdb.apache.org
> Subject: Re: [VOTE] Charta and proposal for first VP
>
> +1
>
>
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> -原始邮件-
> 发件人: "Julian Feinauer" 
> 发送时间: 2020-09-03 19:19:45 (星期四)
> 收件人: "dev@iotdb.apache.org" 
> 抄送:
> 主题: Re: [VOTE] Charta and proposal for first VP
>
> +1 (binding)
>
> Julian
>
> Am 03.09.20, 13:14 schrieb "Dawei Liu" :
>
> Hi,
>
>
> +1
>
>
> Best,
> Dawei
> On 09/03/2020 18:57, Julian Feinauer wrote:
> Hi all,
>
> as the discussion in the thread calmed down quite a bit and there
> was no real controvercy I decided to start a formal Vote on our Charta and
> who we want to suggest to the board as initial VP for Apache IoTDB.
>
> From the discuss thread (
> https://lists.apache.org/thread.html/reeac2c6d33d3b7fe3807ded35165f4ee62c3814448ed7b3272672506%40%3Cdev.iotdb.apache.org%3E)
> there is the clear favorit (and only nomination):
>
> Charta: an IoT native database with high performance for data
> management and analysis, on the edge and the cloud.
>
> VP: Xiangdong Huang
>
> As I already stated in the discuss thread I think both choices are
> excellent.
>
> What does the community think?
>
> +1 for YES, Xiangdong as VP and Charta as above
> -1 for NO and please make another suggestion then, so that we can
> move the discussion further
>
> As usual, the Vote will be open for at least 72hrs.
>
> Best
> Julian
>
>
>
>
> --
> Best,
> Xiangwei Wei

Re: [VOTE] Start the graduation process

[Gaofei Cao]

Hi,

big +1 from PPMC.

Best,

--
Gaofei Cao

Dawei Liu  于2020年8月31日周一 上午9:58写道：
>
> Hi，
>
>
> big +1
>
>
> Best,
> ———
> Dawei Liu
>
>
>
>
> On 08/31/2020 09:55，Xiangdong Huang wrote：
> Hi,
>
> big +1 from PPMC.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> 袁骏  于2020年8月31日周一 上午9:51写道：
>
> Hi,
>
>
> +1 from PPMC
>
>
> It's been astounding progress for 2 years!
>
>
>
>
>
>
>
> --
>
> 袁骏
> 首席架构师
> 清华大学大数据国家实验室
>
>
> At 2020-08-30 23:54:00, "李天安"  wrote:
> Hi,
>
> +1 from PPMC
>
> Thanks,
>
>
> Best Regards,
> —
> Tianan Li
> School of Software, Tsinghua University
>
>
> 李天安
> 清华大学 软件学院
>
>
> On 08/30/2020 20:46，Julian Feinauer wrote：
> Hi folks,
>
> as we just had a very positive discussion about the maturity of our
> community [1] I want to formally start the vote if we want to start the
> graduation process.
>
> For Information about our maturity assessment please see [2].
>
> Do you agree that the IoTDB project is ready for graduation and that we
> should start the graduation process now?
>
> As usual, this vote will be open for at least 72hrs.
>
> Best
> Julian
>
>
>
> [1]
> https://lists.apache.org/thread.html/r7607cbf6ff2020dc7e7cc27eb698ce265b768ed2a63d3e353c2dc572%40%3Cdev.iotdb.apache.org%3E
> [2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148645763
>
>

Re: Integrate Calcite in IoTDB

[Gaofei Cao]

Hi Julian,

I cloned your repo https://github.com/JulianFeinauer/incubator-iotdb/tree/
calcite-integration, but an error appeared as below.

Could not resolve dependencies for project
>> org.apache.iotdb:iotdb-calcite:jar:0.8.0-SNAPSHOT: Failure to find
>> org.apache.calcite:calcite-core:jar:1.19.0-SNAPSHOT in
>> https://repository.apache.org/snapshots was cached in the local
>> repository, resolution will not be reattempted until the update interval of
>> apache.snapshots has elapsed or updates are forced -> [Help 1]
>
>
>
And I cloned Apache-Calcite, checkout to the branch branch-1.19, executed
`mvn clean install -Dmaven.test.skip=true`, but an error appeared as below.

[ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-dependency-plugin:3.1.1:analyze-only
>> (analyze) on project calcite-linq4j: Dependency problems found -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>
> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
>> command
>
> [ERROR]   mvn  -rf :calcite-linq4j
>
>
> So how to solve this problem. And maybe i think it's better to ask this
problem in Calcite community haha. 

Thanks & Best Regards
Gaofei

Julian Feinauer  于2019年2月28日周四 上午12:23写道：

> Hi Tianan,
>
> personally I found it difficould to learn Calcite from the Documentation,
> but the csv Examples are quite okay to follow.
> I also filed a Jira for this issue [1] and prepared a minimal working
> example for Calcite on top of a tsfile in my fork [2].
>
> The Example in the Repo is fully functional and maps each device from a
> tsfile to one Table and each measurement to a column (+ timestamp).
> It supports basically all SQL Queries.
>
> Of course there is no efficiency yet like predicate pushdown or path
> selection pushdown or so... this is the fun work for the future : )
>
> Best
> Julian
>
> [1] https://issues.apache.org/jira/browse/IOTDB-28
> [2]
> https://github.com/JulianFeinauer/incubator-iotdb/tree/calcite-integration
>
> Am 27.02.19, 16:12 schrieb "李天安" :
>
> Hi Julian,
> Nice to hear from you.
> I’m very glad to hear that you’d like to help us with the
> integration.
> We want to proceed the integration  as follows:
> Firstly, we will learn how you integrate calcite with other
> products from official website.
> After that, we discuss the structure of Calcite Integration with
> you.
>
> Tianan Li
>
> > 在 2019年2月26日，上午4:39，Julian Feinauer 
> 写道：
> >
> > Hi Tianan,
> >
> > nice to hear from you!
> > I just recently recognized how far you have come and how less time I
> commited to IoTDB.
> > I would really love to participate in this effort and help you with
> the Calcite Adapter.
> > What do you think is the best way to proceed?
> > I can tell you something about the structure of Calcite
> Integratioons (or make a walkthrough through the Plc4x integration I’ve
> done).
> >
> > What do the others think?
> >
> > Julian
> >
> > Von: 李天安 
> > Datum: Montag, 25. Februar 2019 um 17:01
> > An: "jfeina...@apache.org" 
> > Betreff: Fwd: Integrate Calcite in IoTDB
> >
> >
> >
> >
> > 下面是被转发的邮件：
> >
> > 发件人: 李天安  lt...@mails.tsinghua.edu.cn>>
> > 主题: Integrate Calcite in IoTDB
> > 日期: 2019年2月25日 GMT+8 下午2:56:56
> > 收件人: dev@iotdb.apache.org
> > 回复－收件人: dev@iotdb.apache.org
> >
> > Hi Julian,
> >
> > My name is Tianan Li, one of the initial committers of IoTDB
> project. Over the past few months, we have optimized the structure and
> content of the IoTDB project and basically completed it. Now we hope to
> integrate with Calcite. I wonder if you would like to instruct us to
> complete the Calcite-IoTDB Adapter.
> >
> > Best
> > Tianan Li
> >
> >
> > 在 2018年12月3日，上午5:25，Julian Feinauer  jfeina...@apache.org>> 写道：
> >
> > Hi,
> >
> > my name is Julian Feinauer and I come from Apache Calcite, Edgent
> and PLC4X. My interest is mostly in time series processing at the edge. In
> my daytime job I work for two companies called pragmatic minds and
> pragmatic industries which we founded nearly 3 years ago in South Germany.
> > I love the idea behind iotDB as it is realy the materialization of
> many of my thoughts about what we really need for efficient storage of ts
> data.
> > I would love to get my hands dirty on the query and filter api and
> perhaps even write a small Calcite Adapter, when I find some time in the
> next weeks.
> >
> > We have 

Re: How to prevent GitBox from sending too many commit notifications

[Gaofei Cao]

+1
I think this way is better

Xiangdong Huang  于2019年1月25日周五 下午9:11写道：

> Hi all,
>
> I find another project has the similar problem, and finally they send all
> code-reviews to the reviews@  (see [1]).
>
> I think that it also fits us. As for the dev@, we can discuss about the
> issues about Infrastructures (e.g., how to use CI, how to keep code
> quality), new features, bugs, performance problems etc. These contents are
> more valuable.
>
> If someone wants to keep tracking with code-reviews or freshman, he can
> subscribe the reviews@ mail list.
>
> For experienced programmers,  they can focus on the contents on dev@
>
> If all of you agree with it, I will try to open a ticket on JIRA INFRA.
>
> Reference:
> [1]
>
> https://issues.apache.org/jira/browse/INFRA-12404?jql=text%20~%20%22github%20review%22%20AND%20%20project%20%20%3D%20Infrastructure
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> 江天  于2019年1月25日周五 上午10:34写道：
>
> > I like the idea of being highly transparent, but we hope to know some
> > tricks of doing this. Do we have to paste the code in the mails or just
> > tell someone what problem which line in which file has? Both of these
> seem
> > tiring.
> >
> > > 在 2019年1月25日，上午1:08，Justin Mclean  写道：
> > >
> > > Hi,
> > >
> > >> No matter what you guys decide to do, I would strongly suggest to take
> > discussions here to the list and not do discussions in the Github
> > code-review tool.
> > >
> > > A very big +1 to this, discussion works best for the whole community if
> > it is on the list.
> > >
> > > Thanks,
> > > Justin
> >
> >
> >
>

Re: Re: How to prevent GitBox from sending too many commit notifications

[Gaofei Cao]

But I have a concern, for new users who subscribed our dev mails list, they
will receive the emails from GitBox frequently, they may be annoying and
unsubscribe our dev mails list :(

张金瑞  于2019年1月24日周四 下午5:29写道：

> A simple way to handle this is to set your own mailbox rules such as auto
> labeling this kind of mails as read and moving them to a specific mail-box
>
>
> 在 2019-01-24 17:25:17，"Gaofei Cao"  写道：
> >Me too. 
> >
> >江天  于2019年1月24日周四 下午5:15写道：
> >
> >> Hello
> >>
> >>
> >> I am driven crazy because every time someone commits to
> incubating-IoTDB,
> >> I receive a mail from GitBox. This is just too annoying. Could someone
> >> please tell me how to disable GitBox’s sending commit notifications, or
> >> make it send to comm...@iotdb.apache.org instead of
> dev@iotdb.apache.org?
> >>
> >>
> >> Thanks
> >>
> >>
> >> Tian Jiang
> >> 2019.1.24
>

Re: How to prevent GitBox from sending too many commit notifications

[Gaofei Cao]

Me too. 

江天  于2019年1月24日周四 下午5:15写道：

> Hello
>
>
> I am driven crazy because every time someone commits to incubating-IoTDB,
> I receive a mail from GitBox. This is just too annoying. Could someone
> please tell me how to disable GitBox’s sending commit notifications, or
> make it send to comm...@iotdb.apache.org instead of dev@iotdb.apache.org?
>
>
> Thanks
>
>
> Tian Jiang
> 2019.1.24