zclllyybb commented on issue #3904: URL: https://github.com/apache/doris-website/issues/3904#issuecomment-4610199302
Breakwater-GitHub-Analysis-Slot: slot_c99895fc08c6 Thanks for the clear report. I verified the issue against the `apache/doris-website` RETENTION page. This is a documentation content bug, not a Doris runtime/setup issue. Findings: - `retention_test2` is declared with only `uid`, `flag`, and `flag2`, so example 4 cannot validly query `date`. To demonstrate "empty aggregation returns NULL", the query should use an existing expression such as `RETENTION(flag)` while keeping `WHERE uid IS NULL`. - Example 3 has inconsistent source data and printed output. Based on the following examples, the printed table appears to be the intended data: example 5 says `flag` is true for `uid = 0`, and example 6 relies on the `uid = 0` row being skipped because `flag2` is NULL. Those statements match `(0, true, NULL), (1, false, false)`, not the current INSERT `(0, false, false), (1, true, NULL)`. - I found the same affected snippet in the current docs and in the version-3.x/version-4.x English plus zh-CN/ja source copies. I did not find an existing related issue or PR in `apache/doris-website`. Suggested next step: A doc-only PR should fix example 4 and then choose one consistent direction for example 3: 1. Preferred: update the INSERT to `(0, true, NULL), (1, false, false)` so the existing printed output and examples 5-7 stay coherent. 2. Alternative: keep the current INSERT, update the example 3 output to `(0, 0, 0)` and `(1, 1, NULL)`, and also adjust the prose in examples 5 and 6 because they currently refer to the wrong `uid`. No query profile or cluster logs are needed to proceed; the markdown content is internally inconsistent enough to confirm the issue. -- 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]
