doc bug: EXPORT_SET example output table has 6 columns but the SQL selects only 1

[boluor]

On the EXPORT_SET page (sql-manual/sql-functions/scalar-functions/string-functions/export-set.md, present in version-4.x and the dev/current docs), one example does not match its own output:

SELECT EXPORT_SET(`bits`, `on`, `off`, `sep`, `num_of_b`)
FROM `test_export_set`;

The SQL selects a single column (the EXPORT_SET(...) result), but the documented output table shows six columns: bits | on | off | sep | num_of_b | ans. So the displayed output cannot be produced by the shown query — running the query as written returns only the ans column.

The output table clearly intends to show the input columns alongside the result (the last column is even aliased ans). Suggested fix — align the SQL with the shown output:

SELECT `bits`, `on`, `off`, `sep`, `num_of_b`,
       EXPORT_SET(`bits`, `on`, `off`, `sep`, `num_of_b`) AS ans
FROM `test_export_set`;

(EN + ZH, both version-4.x and dev/current.) Filing separately from the setup-data change for this page so the SQL/output correction can be reviewed on its own.

[zclllyybb]

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.