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

   ## Summary
   
   Two materialized-view pages had examples that could not run on a fresh 
cluster because they reference TPC-H base tables (\`lineitem\`, \`orders\`, 
\`partsupp\`) that the pages never create. The async page additionally 
hard-codes \`STARTS '2024-12-01 20:30:00'\`, which is in the past on any 
cluster running after Dec 2024 and is rejected with *\"starts time must be 
greater than current time\"*.
   
   | File | Change |
   |------|--------|
   | \`sync-materialized-view/CREATE-MATERIALIZED-VIEW.md\` (EN + ZH) | Added a 
TPC-H-style \`lineitem\` setup block at the top of \`## Example\`. \`desc 
lineitem\` now matches the documented schema exactly and the subsequent 
\`CREATE MATERIALIZED VIEW sync_agg_mv\` succeeds. |
   | \`async-materialized-view/CREATE-ASYNC-MATERIALIZED-VIEW.md\` (EN + ZH) | 
Added TPC-H-style \`orders\` (partitioned by \`o_orderdate\`), \`lineitem\` and 
\`partsupp\` setup blocks at the top of \`## Examples\`. Example 2's later 
\`CREATE TABLE IF NOT EXISTS orders\` becomes a no-op rather than a duplicate 
definition. Also bumped all three \`STARTS '2024-12-01 20:30:00'\` to \`STARTS 
'2099-01-01 20:30:00'\` so the scheduled refresh time is in the future, which 
the planner requires. |
   
   ## Verification
   
   End-to-end on a single-node Apache Doris 4.1.1 cluster: with the new setup, 
\`desc lineitem\`, \`CREATE MATERIALIZED VIEW sync_agg_mv\` and \`CREATE 
MATERIALIZED VIEW complete_mv\` all succeed without errors.
   
   ## Test plan
   
   - [x] Run each setup + example on 4.1.1; no errors.
   - [x] EN and ZH parallel edited.
   - [x] No existing examples removed.
   
   🤖 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