Visitar URL original
4.0.6 Release Notes · Issue #64065 · apache/doris · GitHub
Skip to content

4.0.6 Release Notes #64065

Description

@morningman

4.0.5 release notes

4.0.6 Release Notes

Apache Doris 4.0.6 is a maintenance release in the 4.0 series. It focuses on stability and operational experience. All 4.0.x users are advised to upgrade, and users running the compute-storage decoupled (cloud) mode benefit the most.

Highlights of this release include:

  • Compute-storage decoupling enhancements: support read-write separation for Compaction, optimize Tablet scheduling and FE-side memory usage, and reduce RPC pressure on the Meta Service.
  • Operational observability: add Compaction task tracking (System Table and HTTP API), a dynamic enable_recycler switch, online adjustment of the memtable flush thread pool, and several brpc / bvar metrics.
  • Data lineage: introduce a Lineage SPI collection framework.
  • Many correctness and stability fixes: cover incorrect query results, load data loss (such as Broker Load loading only the first file, and PostgreSQL DML being silently dropped), crashes, hangs, and resource leaks.

Before upgrading, read the Behavior Changes section below, which contains several adjustments to default values and privileges.

Behavior Changes

New Features & Improvements

Functions & Types

Query Optimization

Storage & Compaction

Compute-Storage Decoupling (Cloud Mode)

Lakehouse

Data Lineage

Observability & Operations

Security & Authentication

Important Bug Fixes

Query Result Correctness

Views

Functions & Types

Variant Type

Load & Streaming

Data Loss / Integrity

Hangs / Leaks

Restart & Metadata

Routine Load / Parsing

Storage & Compaction

Compute-Storage Decoupling (Cloud Mode)

Lakehouse & External Data Sources

File Cache & IO

Metadata & Job System

Security & Authentication

Stability & Misc

These notes focus on user-visible and operations-visible changes, and omit some purely-internal refactoring and fixes with no external symptoms. For the complete commit history, refer to the PR list for 4.0.6 in the apache/doris repository on GitHub.

Activity

  1. zclllyybb commented on Jun 3, 2026

    @zclllyybb
    Contributor

    Breakwater-GitHub-Analysis-Slot: slot_7e689c9aedcd

    Initial analysis: this issue looks like a release-notes draft/tracking item for Apache Doris 4.0.6, not a runtime bug report or a request for a code fix.

    I checked the live issue metadata. It is open, has no labels, no milestone, no assignees, and no existing discussion. The body links back to the 4.0.5 release notes, has a clear Behavior Changes section, and covers the main user-visible areas for 4.0.6: cloud-mode improvements, observability, lineage, correctness fixes, load/integrity fixes, storage/compaction fixes, lakehouse fixes, security updates, and stability fixes.

    One release-process gap to confirm before publication: I can see public 4.0.6-rc01 and 4.0.6-rc02 tags, but I did not find a published GitHub release named 4.0.6 at the time of this check. So the notes should not be treated as final unless the release manager has already fixed the final artifact/tag boundary elsewhere.

    Suggested maintainer actions:

    • Add the same process metadata used by the previous release-notes issue, at least the release notes label, and a milestone if the project uses one for 4.0.x maintenance releases.
    • Confirm that every referenced PR is included in the final 4.0.6 release/cherry-pick range, especially the Behavior Changes and data-loss/correctness fixes.
    • Add or link the final release artifact/tag/checksum page once available. If this is still RC-stage content, make that explicit in the issue or keep the issue open until the final release is published.
    • Double-check the Behavior Changes wording before closing: enable_strict_consistency_dml default change, Time Series Compaction threshold change, segments_key_bounds_truncation_threshold, Cluster Snapshot root privilege requirement, and JSONB/Variant distribution-column rejection are the items most likely to affect upgrade planning.
    • After the final release is published, close this tracking issue or link it from the official release announcement so users have a stable destination.

    No query logs, BE/FE logs, profiles, or reproduction steps are needed for this issue unless maintainers want to audit a specific listed fix. The main missing information is release-process metadata and confirmation that the PR list matches the final 4.0.6 artifact.

  2. DalongZhenZ commented on Jun 11, 2026

    @DalongZhenZ
    Contributor

    this is 4.0.6 release ,the fist line witre wrong @morningman

  3. morningman commented on Jul 9, 2026

    @morningman
    ContributorAuthor

    this is 4.0.6 release ,the fist line witre wrong @morningman

    thanks. but first line is just a link to previous release notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions