[ANNOUNCE] Apache IoTDB 1.2.1 released

2023-09-18 Thread 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

[RESULT][VOTE] Release Apache IoTDB 1.2.1

2023-09-18 Thread 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

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

2023-09-18 Thread Xiangdong Huang 
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
> > 
> > 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
> > >
> >
>

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

2023-09-18 Thread 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
> >
>

Re: [VOTE] Apache IoTDB 1.2.1 RC1 release

2023-09-18 Thread 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

2023-09-18 Thread 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