You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by Steve Su <st...@qq.com.INVALID> on 2022/02/18 02:44:18 UTC

[DISCUSS] Release IoTDB v0.12.5

Hi all,

It has been 2 months after the v0.12.4 release, and we can see many bug fixes and improvements have been introduced in the rel/0.12 branch.
    
Here is the change list:

# New Features
* [IOTDB-2078] Split large TsFile tool
* [IOTDB-2192] Support extreme function

# Improvements
* [IOTDB-1297] Refactor the memory control when enabling time partitions
* [IOTDB-2195] Control the concurrent query execution thread
* [IOTDB-2475] Remove sg not ready log in batch process
* [IOTDB-2502] Add query sql in error log if encountering exception
* [IOTDB-2506] Refine the lock granularity of the aggregation query
* [IOTDB-2534] add character support while using double quote
* [IOTDB-2562] Change default value of sync mlog period parameter
* Avoid too many warning logs being printed, when opening too many file handlers

# Bug Fixes
* [IOTDB-1960] Fix count timeseries bug in cluster mode
* [IOTDB-2174] Fix Regexp filter serializing and deserializing error
* [IoTDB-2185] fix get an exception bug when parsing the header of CSV
* [IOTDB-2194] Fix SHOW TIMESERIES will only display 2000 timeseries in cluster mode
* [IOTDB-2197] Fix datatype conversion exception in Spark Connector
* [IOTDB-2209] Fix logback CVE-2021-42550 issue
* [IOTDB-2219] Fix query in-memory data is incorrect in cluster mode
* [IOTDB-2222] Fix OOM and data was written in incorrectly bugs of Spark Connector
* [IOTDB-2251] [IOTDB-2252] Fix Query deadlock
* [IOTDB-2282] fix tag recover bug after tag update
* [IOTDB-2320] MemoryLeak cause by wal Scheduled trim task thread
* [IOTDB-2381] Fix deadlock caused by incorrect buffer pool size counter
* [IOTDB-2400] Fix series reader bug
* [IOTDB-2426] WAL deadlock caused by too many open files
* [IOTDB-2445] Fix overlapped data should be consumed first bug
* [IOTDB-2499] Fix division by zero error when recovering merge
* [IOTDB-2507] Fix NPE when merge recover
* [IOTDB-2528] Fix MLog corruption and recovery bug after killing system
* [IOTDB-2532] Fix query with align by device can't get value after clear cache
* [IOTDB-2533] Fix change max_deduplicated_path_num does not take effect
* [IOTDB-2544] Fix tag info sync error during metadata sync
* [IOTDB-2550] Avoid show timeseries error after alter tag on sync sender
* Fix a logical bug in processPlanLocally in cluster mode
* Throw Exception while using last query with align by device
* Add a judgement to determine raft log size can fit into buffer before log appending in cluster mode
* Fix grafana can't be used bug
    
I think it's time to release v0.12.5. How do you think?

Best,
Steve Yurong Su
Tsinghua University

Re: Re: [DISCUSS] Release IoTDB v0.12.5

Posted by "limeng32@live.cn" <li...@live.cn>.
+1



limeng32@live.cn
 
From: Chao Wang
Date: 2022-02-18 11:32
To: dev@iotdb.apache.org
CC: dev@iotdb.apache.org
Subject: Re: [DISCUSS] Release IoTDB v0.12.5
+1, Looking forward to the v0.12.5
 
 
 
 
Thanks!
 
 
Chao Wang
BONC ltd
ccgowork@163.com
On 2/18/2022 11:09,Houliang Qi<ne...@163.com> wrote:
+1, Looking forward to the v0.12.5
 
 
 
 
Thanks,
---------------------------------------
Houliang Qi
BONC, Ltd
On 02/18/2022 11:03,Haonan Hou<hh...@qq.com.INVALID> wrote:
+1 for v0.12.5
 
Best.
Haonan Hou
 
On Feb 18, 2022, at 10:44 AM, Steve Su <st...@qq.com.INVALID> wrote:
 
Hi all,
 
It has been 2 months after the v0.12.4 release, and we can see many bug fixes and improvements have been introduced in the rel/0.12 branch.
 
Here is the change list:
 
# New Features
* [IOTDB-2078] Split large TsFile tool
* [IOTDB-2192] Support extreme function
 
# Improvements
* [IOTDB-1297] Refactor the memory control when enabling time partitions
* [IOTDB-2195] Control the concurrent query execution thread
* [IOTDB-2475] Remove sg not ready log in batch process
* [IOTDB-2502] Add query sql in error log if encountering exception
* [IOTDB-2506] Refine the lock granularity of the aggregation query
* [IOTDB-2534] add character support while using double quote
* [IOTDB-2562] Change default value of sync mlog period parameter
* Avoid too many warning logs being printed, when opening too many file handlers
 
# Bug Fixes
* [IOTDB-1960] Fix count timeseries bug in cluster mode
* [IOTDB-2174] Fix Regexp filter serializing and deserializing error
* [IoTDB-2185] fix get an exception bug when parsing the header of CSV
* [IOTDB-2194] Fix SHOW TIMESERIES will only display 2000 timeseries in cluster mode
* [IOTDB-2197] Fix datatype conversion exception in Spark Connector
* [IOTDB-2209] Fix logback CVE-2021-42550 issue
* [IOTDB-2219] Fix query in-memory data is incorrect in cluster mode
* [IOTDB-2222] Fix OOM and data was written in incorrectly bugs of Spark Connector
* [IOTDB-2251] [IOTDB-2252] Fix Query deadlock
* [IOTDB-2282] fix tag recover bug after tag update
* [IOTDB-2320] MemoryLeak cause by wal Scheduled trim task thread
* [IOTDB-2381] Fix deadlock caused by incorrect buffer pool size counter
* [IOTDB-2400] Fix series reader bug
* [IOTDB-2426] WAL deadlock caused by too many open files
* [IOTDB-2445] Fix overlapped data should be consumed first bug
* [IOTDB-2499] Fix division by zero error when recovering merge
* [IOTDB-2507] Fix NPE when merge recover
* [IOTDB-2528] Fix MLog corruption and recovery bug after killing system
* [IOTDB-2532] Fix query with align by device can't get value after clear cache
* [IOTDB-2533] Fix change max_deduplicated_path_num does not take effect
* [IOTDB-2544] Fix tag info sync error during metadata sync
* [IOTDB-2550] Avoid show timeseries error after alter tag on sync sender
* Fix a logical bug in processPlanLocally in cluster mode
* Throw Exception while using last query with align by device
* Add a judgement to determine raft log size can fit into buffer before log appending in cluster mode
* Fix grafana can't be used bug
 
I think it's time to release v0.12.5. How do you think?
 
Best,
Steve Yurong Su
Tsinghua University

Re: [DISCUSS] Release IoTDB v0.12.5

Posted by Chao Wang <cc...@163.com>.
+1, Looking forward to the v0.12.5




Thanks!


Chao Wang
BONC ltd
ccgowork@163.com
On 2/18/2022 11:09,Houliang Qi<ne...@163.com> wrote:
+1, Looking forward to the v0.12.5




Thanks,
---------------------------------------
Houliang Qi
BONC, Ltd
On 02/18/2022 11:03,Haonan Hou<hh...@qq.com.INVALID> wrote:
+1 for v0.12.5

Best.
Haonan Hou

On Feb 18, 2022, at 10:44 AM, Steve Su <st...@qq.com.INVALID> wrote:

Hi all,

It has been 2 months after the v0.12.4 release, and we can see many bug fixes and improvements have been introduced in the rel/0.12 branch.

Here is the change list:

# New Features
* [IOTDB-2078] Split large TsFile tool
* [IOTDB-2192] Support extreme function

# Improvements
* [IOTDB-1297] Refactor the memory control when enabling time partitions
* [IOTDB-2195] Control the concurrent query execution thread
* [IOTDB-2475] Remove sg not ready log in batch process
* [IOTDB-2502] Add query sql in error log if encountering exception
* [IOTDB-2506] Refine the lock granularity of the aggregation query
* [IOTDB-2534] add character support while using double quote
* [IOTDB-2562] Change default value of sync mlog period parameter
* Avoid too many warning logs being printed, when opening too many file handlers

# Bug Fixes
* [IOTDB-1960] Fix count timeseries bug in cluster mode
* [IOTDB-2174] Fix Regexp filter serializing and deserializing error
* [IoTDB-2185] fix get an exception bug when parsing the header of CSV
* [IOTDB-2194] Fix SHOW TIMESERIES will only display 2000 timeseries in cluster mode
* [IOTDB-2197] Fix datatype conversion exception in Spark Connector
* [IOTDB-2209] Fix logback CVE-2021-42550 issue
* [IOTDB-2219] Fix query in-memory data is incorrect in cluster mode
* [IOTDB-2222] Fix OOM and data was written in incorrectly bugs of Spark Connector
* [IOTDB-2251] [IOTDB-2252] Fix Query deadlock
* [IOTDB-2282] fix tag recover bug after tag update
* [IOTDB-2320] MemoryLeak cause by wal Scheduled trim task thread
* [IOTDB-2381] Fix deadlock caused by incorrect buffer pool size counter
* [IOTDB-2400] Fix series reader bug
* [IOTDB-2426] WAL deadlock caused by too many open files
* [IOTDB-2445] Fix overlapped data should be consumed first bug
* [IOTDB-2499] Fix division by zero error when recovering merge
* [IOTDB-2507] Fix NPE when merge recover
* [IOTDB-2528] Fix MLog corruption and recovery bug after killing system
* [IOTDB-2532] Fix query with align by device can't get value after clear cache
* [IOTDB-2533] Fix change max_deduplicated_path_num does not take effect
* [IOTDB-2544] Fix tag info sync error during metadata sync
* [IOTDB-2550] Avoid show timeseries error after alter tag on sync sender
* Fix a logical bug in processPlanLocally in cluster mode
* Throw Exception while using last query with align by device
* Add a judgement to determine raft log size can fit into buffer before log appending in cluster mode
* Fix grafana can't be used bug

I think it's time to release v0.12.5. How do you think?

Best,
Steve Yurong Su
Tsinghua University

Re: [DISCUSS] Release IoTDB v0.12.5

Posted by Houliang Qi <ne...@163.com>.
+1, Looking forward to the v0.12.5




Thanks,
---------------------------------------
Houliang Qi
BONC, Ltd
On 02/18/2022 11:03,Haonan Hou<hh...@qq.com.INVALID> wrote:
+1 for v0.12.5

Best.
Haonan Hou

On Feb 18, 2022, at 10:44 AM, Steve Su <st...@qq.com.INVALID> wrote:

Hi all,

It has been 2 months after the v0.12.4 release, and we can see many bug fixes and improvements have been introduced in the rel/0.12 branch.

Here is the change list:

# New Features
* [IOTDB-2078] Split large TsFile tool
* [IOTDB-2192] Support extreme function

# Improvements
* [IOTDB-1297] Refactor the memory control when enabling time partitions
* [IOTDB-2195] Control the concurrent query execution thread
* [IOTDB-2475] Remove sg not ready log in batch process
* [IOTDB-2502] Add query sql in error log if encountering exception
* [IOTDB-2506] Refine the lock granularity of the aggregation query
* [IOTDB-2534] add character support while using double quote
* [IOTDB-2562] Change default value of sync mlog period parameter
* Avoid too many warning logs being printed, when opening too many file handlers

# Bug Fixes
* [IOTDB-1960] Fix count timeseries bug in cluster mode
* [IOTDB-2174] Fix Regexp filter serializing and deserializing error
* [IoTDB-2185] fix get an exception bug when parsing the header of CSV
* [IOTDB-2194] Fix SHOW TIMESERIES will only display 2000 timeseries in cluster mode
* [IOTDB-2197] Fix datatype conversion exception in Spark Connector
* [IOTDB-2209] Fix logback CVE-2021-42550 issue
* [IOTDB-2219] Fix query in-memory data is incorrect in cluster mode
* [IOTDB-2222] Fix OOM and data was written in incorrectly bugs of Spark Connector
* [IOTDB-2251] [IOTDB-2252] Fix Query deadlock
* [IOTDB-2282] fix tag recover bug after tag update
* [IOTDB-2320] MemoryLeak cause by wal Scheduled trim task thread
* [IOTDB-2381] Fix deadlock caused by incorrect buffer pool size counter
* [IOTDB-2400] Fix series reader bug
* [IOTDB-2426] WAL deadlock caused by too many open files
* [IOTDB-2445] Fix overlapped data should be consumed first bug
* [IOTDB-2499] Fix division by zero error when recovering merge
* [IOTDB-2507] Fix NPE when merge recover
* [IOTDB-2528] Fix MLog corruption and recovery bug after killing system
* [IOTDB-2532] Fix query with align by device can't get value after clear cache
* [IOTDB-2533] Fix change max_deduplicated_path_num does not take effect
* [IOTDB-2544] Fix tag info sync error during metadata sync
* [IOTDB-2550] Avoid show timeseries error after alter tag on sync sender
* Fix a logical bug in processPlanLocally in cluster mode
* Throw Exception while using last query with align by device
* Add a judgement to determine raft log size can fit into buffer before log appending in cluster mode
* Fix grafana can't be used bug

I think it's time to release v0.12.5. How do you think?

Best,
Steve Yurong Su
Tsinghua University

Re: [DISCUSS] Release IoTDB v0.12.5

Posted by Haonan Hou <hh...@qq.com.INVALID>.
+1 for v0.12.5

Best.
Haonan Hou

> On Feb 18, 2022, at 10:44 AM, Steve Su <st...@qq.com.INVALID> wrote:
> 
> Hi all,
> 
> It has been 2 months after the v0.12.4 release, and we can see many bug fixes and improvements have been introduced in the rel/0.12 branch.
> 
> Here is the change list:
> 
> # New Features
> * [IOTDB-2078] Split large TsFile tool
> * [IOTDB-2192] Support extreme function
> 
> # Improvements
> * [IOTDB-1297] Refactor the memory control when enabling time partitions
> * [IOTDB-2195] Control the concurrent query execution thread
> * [IOTDB-2475] Remove sg not ready log in batch process
> * [IOTDB-2502] Add query sql in error log if encountering exception
> * [IOTDB-2506] Refine the lock granularity of the aggregation query
> * [IOTDB-2534] add character support while using double quote
> * [IOTDB-2562] Change default value of sync mlog period parameter
> * Avoid too many warning logs being printed, when opening too many file handlers
> 
> # Bug Fixes
> * [IOTDB-1960] Fix count timeseries bug in cluster mode
> * [IOTDB-2174] Fix Regexp filter serializing and deserializing error
> * [IoTDB-2185] fix get an exception bug when parsing the header of CSV
> * [IOTDB-2194] Fix SHOW TIMESERIES will only display 2000 timeseries in cluster mode
> * [IOTDB-2197] Fix datatype conversion exception in Spark Connector
> * [IOTDB-2209] Fix logback CVE-2021-42550 issue
> * [IOTDB-2219] Fix query in-memory data is incorrect in cluster mode
> * [IOTDB-2222] Fix OOM and data was written in incorrectly bugs of Spark Connector
> * [IOTDB-2251] [IOTDB-2252] Fix Query deadlock
> * [IOTDB-2282] fix tag recover bug after tag update
> * [IOTDB-2320] MemoryLeak cause by wal Scheduled trim task thread
> * [IOTDB-2381] Fix deadlock caused by incorrect buffer pool size counter
> * [IOTDB-2400] Fix series reader bug
> * [IOTDB-2426] WAL deadlock caused by too many open files
> * [IOTDB-2445] Fix overlapped data should be consumed first bug
> * [IOTDB-2499] Fix division by zero error when recovering merge
> * [IOTDB-2507] Fix NPE when merge recover
> * [IOTDB-2528] Fix MLog corruption and recovery bug after killing system
> * [IOTDB-2532] Fix query with align by device can't get value after clear cache
> * [IOTDB-2533] Fix change max_deduplicated_path_num does not take effect
> * [IOTDB-2544] Fix tag info sync error during metadata sync
> * [IOTDB-2550] Avoid show timeseries error after alter tag on sync sender
> * Fix a logical bug in processPlanLocally in cluster mode
> * Throw Exception while using last query with align by device
> * Add a judgement to determine raft log size can fit into buffer before log appending in cluster mode
> * Fix grafana can't be used bug
> 
> I think it's time to release v0.12.5. How do you think?
> 
> Best,
> Steve Yurong Su
> Tsinghua University


Re: [DISCUSS] Release IoTDB v0.12.5

Posted by Steve Su <st...@qq.com.INVALID>.
Hi,

Thanks for your votes. We have got 6 +1 votes. 

I will start the official release process of v0.12.5. Please stay tuned for upcoming RC versions :D

Thanks,
Steve Su

------------------ Original ------------------
From: "dev" <st...@qq.com.INVALID>;
Date: Fri, Feb 18, 2022 10:44 AM
To: "dev"<de...@iotdb.apache.org>;
Subject: [DISCUSS] Release IoTDB v0.12.5

Hi all,

It has been 2 months after the v0.12.4 release, and we can see many bug fixes and improvements have been introduced in the rel/0.12 branch.

Here is the change list:

# New Features
* [IOTDB-2078] Split large TsFile tool
* [IOTDB-2192] Support extreme function

# Improvements
* [IOTDB-1297] Refactor the memory control when enabling time partitions
* [IOTDB-2195] Control the concurrent query execution thread
* [IOTDB-2475] Remove sg not ready log in batch process
* [IOTDB-2502] Add query sql in error log if encountering exception
* [IOTDB-2506] Refine the lock granularity of the aggregation query
* [IOTDB-2534] add character support while using double quote
* [IOTDB-2562] Change default value of sync mlog period parameter
* Avoid too many warning logs being printed, when opening too many file handlers

# Bug Fixes
* [IOTDB-1960] Fix count timeseries bug in cluster mode
* [IOTDB-2174] Fix Regexp filter serializing and deserializing error
* [IoTDB-2185] fix get an exception bug when parsing the header of CSV
* [IOTDB-2194] Fix SHOW TIMESERIES will only display 2000 timeseries in cluster mode
* [IOTDB-2197] Fix datatype conversion exception in Spark Connector
* [IOTDB-2209] Fix logback CVE-2021-42550 issue
* [IOTDB-2219] Fix query in-memory data is incorrect in cluster mode
* [IOTDB-2222] Fix OOM and data was written in incorrectly bugs of Spark Connector
* [IOTDB-2251] [IOTDB-2252] Fix Query deadlock
* [IOTDB-2282] fix tag recover bug after tag update
* [IOTDB-2320] MemoryLeak cause by wal Scheduled trim task thread
* [IOTDB-2381] Fix deadlock caused by incorrect buffer pool size counter
* [IOTDB-2400] Fix series reader bug
* [IOTDB-2426] WAL deadlock caused by too many open files
* [IOTDB-2445] Fix overlapped data should be consumed first bug
* [IOTDB-2499] Fix division by zero error when recovering merge
* [IOTDB-2507] Fix NPE when merge recover
* [IOTDB-2528] Fix MLog corruption and recovery bug after killing system
* [IOTDB-2532] Fix query with align by device can't get value after clear cache
* [IOTDB-2533] Fix change max_deduplicated_path_num does not take effect
* [IOTDB-2544] Fix tag info sync error during metadata sync
* [IOTDB-2550] Avoid show timeseries error after alter tag on sync sender
* Fix a logical bug in processPlanLocally in cluster mode
* Throw Exception while using last query with align by device
* Add a judgement to determine raft log size can fit into buffer before log appending in cluster mode
* Fix grafana can't be used bug

I think it's time to release v0.12.5. How do you think?

Best,
Steve Yurong Su
Tsinghua University