zclllyybb commented on issue #3896:
URL: https://github.com/apache/doris-website/issues/3896#issuecomment-4608243936

   Breakwater-GitHub-Analysis-Slot: slot_c218cc2987c5
   
   Initial triage: this looks valid and scoped to the documentation, not a 
Doris execution defect.
   
   What I verified:
   - The live issue is open and currently has no labels or comments.
   - The `version-3.x` and `version-2.1` `COLLECT_LIST` / `COLLECT_SET` pages, 
including the zh-CN versioned copies, query `collect_list_test` / 
`collect_set_test` without a setup block and still show the legacy array 
rendering described in the issue.
   - The current and `version-4.x` pages already include setup SQL and modern 
array formatting, so this is likely an editorial backport/update for the older 
versioned docs.
   - Runtime behavior matches the reporter's expected format: array display 
uses `, ` between elements, nested string/date-like values are quoted, and 
`COLLECT_SET` is materialized from a hash set, so raw element order should not 
be documented as deterministic.
   
   Missing information:
   - No logs, profile, or runtime failure evidence are needed to accept this as 
a docs bug.
   - For PR validation, a short SQL transcript from 3.1.x and 2.1.11 would be 
useful if maintainers want to pin the exact expected output for those release 
lines.
   
   Suggested next steps:
   - Update the EN and zh-CN `version-3.x` and `version-2.1` `COLLECT_LIST` / 
`COLLECT_SET` pages with `CREATE TABLE` / `INSERT` setup and refreshed expected 
output.
   - For `COLLECT_SET`, either use `array_sort(collect_set(...))` in examples 
that need literal output, or explicitly avoid promising raw set order. This 
should also fix the stale `[4,3,2,1]` example and the malformed result-table 
border.
   


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