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

   Breakwater-GitHub-Analysis-Slot: slot_57321f7a9bda
   
   Initial triage: confirmed as a documentation bug.
   
   I rechecked the live issue and the current upstream `apache/doris-website` 
tree. The reported mismatch is present in these docs:
   
   - 
`docs/sql-manual/sql-functions/scalar-functions/string-functions/export-set.md`
   - 
`versioned_docs/version-4.x/sql-manual/sql-functions/scalar-functions/string-functions/export-set.md`
   - 
`i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-functions/scalar-functions/string-functions/export-set.md`
   - 
`i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/sql-manual/sql-functions/scalar-functions/string-functions/export-set.md`
   
   The example query selects only `EXPORT_SET(...)`, but the documented output 
table contains the five input columns plus `ans`. That output cannot come from 
the shown SQL. This does not look like a Doris runtime/function issue; it is a 
docs example/output alignment issue.
   
   Recommended fix: update the example SQL in the affected EN and ZH 
current/version-4.x pages to select `bits`, `on`, `off`, `sep`, `num_of_b`, and 
`EXPORT_SET(...) AS ans`, matching the existing output table. I also noticed 
the same one-column SQL vs six-column output pattern in the Japanese 
current/version-4.x source files, so it is worth applying the same correction 
there if those pages are maintained from the same example.
   
   No additional logs, profiles, or runtime traces are needed for this triage. 
The only useful verification before closing would be to rerun or manually 
validate the corrected example output from `test_export_set`.
   


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