morningman opened a new pull request, #4186:
URL: https://github.com/apache/doris-website/pull/4186

   ## Versions 
   
   - [x] dev
   - [ ] 4.x
   - [ ] 3.x
   - [ ] 2.1 or older (not covered by version/language sync gate)
   
   ## Languages
   
   - [x] Chinese
   - [x] English
   
   ## Docs Checklist
   
   - [x] Checked by AI
   - [x] Test Cases Built
   - [x] Updated required version and language counterparts, or explained why 
not
   - [x] If only one language changed, confirmed whether source/translation 
counterparts need sync
   
   IVM and the Fluss JNI changes are Doris 5.0 features, so only the dev docs 
(`docs/` and `i18n/zh-CN/.../current`) change.
   
   ## What this PR changes
   
   ### 1. IVM: supported queries (commit `[docs](ivm) Add verified examples 
...`)
   
   The "Supported queries" section of the IVM page used terms such as 
"single-row constant relation" without examples. It now has:
   
   - A shared sample schema (`customers` / `sales` / `refunds`) and, for every 
supported relational operation and aggregate function, a tabbed example with 
its result.
   - Corrections to the supported scope, checked against Doris master 
(7ac0eb2fdb4) and a live cluster:
     - `UNION ALL` with constant branches, `SELECT DISTINCT` and `GROUPING 
SETS` / `ROLLUP` / `CUBE` are supported. The old page listed the first two as 
unsupported and did not mention the third.
     - The unsupported forms are listed precisely: subqueries in 
`WHERE`/`SELECT` (all of them, not only the "Mark Join" case), `WITH`, 
`HAVING`, `INTERSECT`/`EXCEPT`, `LATERAL VIEW`, `COLLECT_LIST(expr, max_size)`.
     - A chained IVM requires the lower IVM to enable Row Binlog and the before 
image.
     - An expression around an aggregate result (`SUM(x) * 100`) can be 
created, but every incremental refresh fails with `PLAN_REWRITE_FAILED`. This 
is documented as a limitation and tracked in apache/doris#68742.
   
   ### 2. IVM: first refresh and baseline rebuild
   
   apache/doris#68390 replaced the MV-level rebuild barrier with a 
per-partition baseline. The page still said that strict `INCREMENTAL` fails 
until `COMPLETE` runs. The section now describes the current behavior, all of 
it checked on a cluster:
   
   - Any first refresh computes all data (strict `INCREMENTAL` included).
   - `TRUNCATE` / `DROP PARTITION` / `RECOVER PARTITION` / strict `REPLACE 
PARTITION` rebuild only the affected MV partitions (`IvmRebuiltPartitions`).
   - Column DDL, table rename/replace, non-strict `REPLACE PARTITION`, and 
property changes that widen the maintained scope put the whole MV in 
`SCHEMA_CHANGE`. The next refresh rebuilds the whole MV, and a strict 
`PARTITIONS` refresh is rejected.
   - `STREAM_UNSUPPORTED` replaces `BINLOG_BROKEN`, which is no longer 
produced. The FAQ and best practices follow the new behavior.
   
   Related reference pages are updated as well: `TASKS` documents 
`IvmRebuiltPartitions`, the IVM link in `CREATE ASYNC MATERIALIZED VIEW` points 
query operators and aggregate functions to "Supported queries" instead of 
"Prerequisites", and the `ALTER ASYNC MATERIALIZED VIEW` note on 
`ivm_partition_window_limit` is fixed.
   
   The IVM page is renamed to `.mdx` in both locales in a separate commit 
(`[docs](ivm) Rename the IVM page to .mdx`, content unchanged) because Tabs 
need MDX and the zh-CN file must keep the same name as the EN source. Review 
the content commit on its own for a readable diff of the page.
   
   ### 3. Fluss: BE JVM heap, JNI heap admission and connection reuse (commit 
`[doc](fluss) ...`)
   
   Adds the user-visible parts of apache/doris#68710, #68711, #68712 and #68713 
to the Fluss Catalog page (EN and zh-CN).
   
   > [!IMPORTANT]
   > apache/doris#68710 and #68713 are still open. Do not merge this PR before 
they are merged.
   
   ## Validation
   
   - Every SQL statement and result in the "Supported queries" section was 
extracted from the page and run on a Doris master build in a fresh database. 
All 22 result blocks match the actual output.
   - All examples were also refreshed with strict `INCREMENTAL` after inserts, 
updates and deletes. Their contents matched a direct query, and the documented 
fallbacks (`MIN_MAX_BOUNDARY_HIT`, `BITMAP_AGG_DELETE`, `PLAN_REWRITE_FAILED`) 
were reproduced.
   - The baseline behaviors (first refresh in every mode, partition and 
whole-MV invalidation, `SCHEMA_CHANGE`, strict `PARTITIONS` rejection, property 
widening) were each reproduced on the cluster.
   - Each changed page was compiled with Docusaurus's MDX pipeline. All 40 
anchor links in the changed pages resolve, the EN and zh-CN IVM pages have the 
same structure and identical code blocks, and `git diff --check` is clean.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to