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

   ## Versions 
   
   - [x] dev
   - [ ] 4.x
   - [ ] 3.x
   - [ ] 2.1 or older (not covered by version/language sync gate)
   
   The feature ships in 5.0.0 (apache/doris#65418), so only `docs/` and 
`i18n/.../current` are touched.
   
   ## Languages
   
   - [x] Chinese
   - [x] English
   
   ## Docs Checklist
   
   - [x] Checked by AI
   - [ ] 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
   
   ## What changed and why
   
   User documentation for the 5.0 row-level change data features (Row Binlog, 
Table Stream, `@incr` incremental query). Facts were checked against 
apache/doris master as of 2026-09-14 (`AlterOp.allowOpRowBinlog`, the stream 
DDL commands, `binlog_block_reader_utils.h`, and the regression suites under 
`binlog/` and `table_stream/`).
   
   New user guide category **Change Data & Table Stream** (zh-CN: 数据变更与增量消费) 
under *Use Doris*, after *Data Update & Delete*, six pages in both languages:
   
   | Page | Content |
   |---|---|
   | `overview` | the problem, the two layers (Row Binlog → Table Stream / 
`@incr`), scenario table, table-model and consumption-type matrices, 
prerequisites, FAQ |
   | `quick-start` | orders-table walkthrough: create table with Row Binlog, 
create Stream, write two batches, read `UPDATE_BEFORE` / `UPDATE_AFTER` / 
`DELETE` / `APPEND`, consume with `INSERT ... SELECT`, check 
`table_stream_consumption` |
   | `row-binlog` | `binlog.*` properties, supported models (DUP, MoW without 
cluster key) and column limits, change record model with hidden columns, DDL 
restrictions, retention (TTL not effective yet), write overhead, `binlog()` TVF 
marked debug-only, error lookup table |
   | `incremental-query` | `t@incr(startTimestamp, endTimestamp, 
incrementType)` with `APPEND_ONLY` / `MIN_DELTA` / `DETAIL`, folding rules, 
examples, limits |
   | `table-stream` | CREATE / SHOW / ALTER / DROP STREAM, `append_only` / 
`min_delta` / `detail` on the same data, `show_initial_rows`, SELECT vs `INSERT 
... SELECT` semantics, virtual columns, FAQ |
   | `table-stream-advanced` | partition-level offsets and `LAG`, `@snapshot()` 
/ `@reset()`, consistent dimension joins, concurrency, effect of base-table 
DDL, monitoring and recovery, error table |
   
   Reference pages: `CREATE/ALTER/DROP-STREAM`, `SHOW-STREAMS`, 
`SHOW-CREATE-STREAM` (new `stream/` folder under table-and-view), the `binlog` 
TVF, `information_schema.table_streams` / `table_stream_consumption`, plus 
three `binlog.*` rows in `CREATE-TABLE.md`. `sidebars.ts` and `current.json` 
gain the category, the *Table Stream* statement group, the TVF and the two 
system tables.
   
   Editorial decisions reflected in the text: FE switches 
`enable_feature_binlog` / `enable_table_stream` documented as default-off 
(restart FE); Row Binlog can only be enabled at `CREATE TABLE`; 
`binlog.ttl_seconds` / `max_bytes` / `max_history_nums` documented as "no 
effect in the current version"; `binlog()` is debug-only; `@incr` is documented 
for the integrated storage-compute mode only; time travel (`FOR TIME AS OF`) is 
intentionally not documented yet.
   
   The last commit restructures all six pages with the repo's doc-optimize 
workflow (prerequisites / step overview / FAQ / error tables, per-section 
knowledge-type comments, `keywords`, links to the STREAM reference pages) 
without changing any command, output or error string. Both language trees have 
the same headings, tables and comments.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01BjEn6JqDkb3pUUw4D6W3Nq
   


-- 
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