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

   The `LAG`, `LEAD`, `NTILE`, `RANK` and `ROW_NUMBER` window-function pages 
each show a `SELECT ... FROM <table>` example with an expected result, but 
never define the table on the page. As written these examples cannot be run or 
reproduced — a reader who copies them gets `Table [...] does not exist`.
   
   This PR adds the missing `CREATE TABLE` + `INSERT` for each table, carried 
in a standard HTML comment (`<!-- setup-sql ... -->`) just before the example. 
Because it is an HTML comment, **the rendered page is unchanged** and **no 
documented expected output is modified** — it only records the data the 
examples already assume, making each example self-contained and reproducible.
   
   Table contents were reverse-derived from the output already printed on each 
page and verified end-to-end on the matching release cluster for every doc tree.
   
   ### Pages and tables
   | Function | Table |
   | --- | --- |
   | `LAG` / `LEAD` | `stock_ticker` |
   | `NTILE` | `student_scores` |
   | `RANK` | `employees` |
   | `ROW_NUMBER` | `int_t` |
   
   Each page is updated in EN + ZH across the dev/`current`, `version-4.x`, 
`version-3.x` and `version-2.1` doc trees (40 files). Verification clusters: 
4.1.1 (4.x), 3.1.4 (3.x), 2.1.11 (2.1), master build (dev). On every tree the 
affected examples failed with "table does not exist" before this change and 
pass (output matches the doc) after it. No `ja-source` changes.
   
   🤖 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