doc bug: ARRAY_MAP example SQL selects one column but the output shows two (version-3.x/2.1)

[boluor]

On the ARRAY_MAP page (scalar-functions/array-functions/array-map.md, version-3.x and version-2.1), one example does not match its own output:

select array_map(x->cast(x as string), c_array1) from test_array_map_function;

+-----------------+-------------------------------------------------------+
| c_array1        | array_map([x] -> CAST(x(0) AS CHARACTER), `c_array1`) |
+-----------------+-------------------------------------------------------+
| [1, 2, 3, 4, 5] | [1, 2, 3, 4, 5]                             |
...

The SQL selects a single column (the array_map(...) result), but the output table has two columns (c_array1 | array_map(...)). Running the query as written returns only the array_map(...) column.

Suggested fix — align the SQL with the shown output:

select c_array1, array_map(x->cast(x as string), c_array1) from test_array_map_function;

(Also note test_array_map_function is never defined on the page; the missing-setup fix for the other array pages is being handled in the Line-B setup PRs, but this page is left out pending the SQL correction above.)

[zclllyybb]

Breakwater-GitHub-Analysis-Slot: slot_c22189f16ba6

I checked the current upstream doris-website content and this looks like a confirmed documentation bug, not a Doris engine behavior issue.

In both affected English pages:

• versioned_docs/version-3.x/sql-manual/sql-functions/scalar-functions/array-functions/array-map.md
• versioned_docs/version-2.1/sql-manual/sql-functions/scalar-functions/array-functions/array-map.md

the example SQL projects only one expression:

select array_map(x->cast(x as string), c_array1) from test_array_map_function;

but the printed result table has two columns: c_array1 plus the array_map(...) result. The suggested SQL is the correct way to align the query with the shown output:

select c_array1, array_map(x->cast(x as string), c_array1) from test_array_map_function;

I also confirmed that test_array_map_function is not defined on the page. PR #3888 covers setup reconstruction for several other array-function pages and explicitly leaves ARRAY_MAP out because of this separate SQL/output mismatch, so this issue still needs its own follow-up.

Recommended next steps:

1. Update the ARRAY_MAP example SQL in the version-3.x and version-2.1 English pages to include c_array1 in the select list.
2. Add a visible setup block for test_array_map_function, or rewrite the example to use a table that is already defined on the page. If the current output should be preserved, the setup needs rows for [1, 2, 3, 4, 5], [6, 7, 8], [], and NULL.
3. Consider applying the same correction to mirrored locale/version copies that contain the same block, so the docs do not drift across languages.

No runtime logs or query profiles are needed for this issue; the fix can be validated by running the corrected docs SQL on the intended 2.1 and 3.x versions and comparing it with the printed output.