Release 1.1.3

In this release, Doris Team has fixed more than 80 issues or performance improvement since 1.1.2. This release is a bugfix release on 1.1 and all users are encouraged to upgrade to this release.

Features

• Support escape identifiers for sqlserver and postgresql in ODBC table.

• Could use Parquet as output file format.

Improvements

• Optimize flush policy to avoid small segments. #12706 #12716

• Refactor runtime filter to reduce the prepare time. #13127

• Lots of memory control related issues during query or load process. #12682 #12688 #12708 #12776 #12782 #12791 #12794 #12820 #12932 #12954 #12951

BugFix

• Core dump on compaction with largeint. #10094

• Grouping sets cause be core or return wrong results. #12313

• PREAGGREGATION flag in orthogonal_bitmap_union_count operator is wrong. #12581

• Level1Iterator should release iterators in heap and it may cause memory leak. #12592

• Fix decommission failure with 2 BEs and existing colocation table. #12644

• BE may core dump because of stack-buffer-overflow when TBrokerOpenReaderResponse too large. #12658

• BE may OOM during load when error code -238 occurs. #12666

• Fix wrong child expression of lead function. #12587

• Fix intersect query failed in row storage code. #12712

• Fix wrong result produced by curdate()/current_date() function. #12720

• Fix lateral view explode_split with temp table bug. #13643

• Bucket shuffle join plan is wrong in two same table. #12930

• Fix bug that tablet version may be wrong when doing alter and load. #13070

• BE core when load data using broker with md5sum()/sm3sum(). #13009

Upgrade Notes

PageCache and ChunkAllocator are disabled by default to reduce memory usage and can be re-enabled by modifying the configuration items disable_storage_page_cache and chunk_reserved_bytes_limit.

Storage Page Cache and Chunk Allocator cache user data chunks and memory preallocation, respectively.

These two functions take up a certain percentage of memory and are not freed. This part of memory cannot be flexibly allocated, which may lead to insufficient memory for other tasks in some scenarios, affecting system stability and availability. Therefore, we disabled these two features by default in version 1.1.3.

However, in some latency-sensitive reporting scenarios, turning off this feature may lead to increased query latency. If you are worried about the impact of this feature on your business after upgrade, you can add the following parameters to be.conf to keep the same behavior as the previous version.

disable_storage_page_cache=false
chunk_reserved_bytes_limit=10%

• disable_storage_page_cache: Whether to disable Storage Page Cache. version 1.1.2 (inclusive), the default is false, i.e., on. version 1.1.3 defaults to true, i.e., off.
• chunk_reserved_bytes_limit: Chunk allocator reserved memory size. 1.1.2 (and earlier), the default is 10% of the overall memory. 1.1.3 version default is 209715200 (200MB).