doc bug: GROUP_ARRAY_INTERSECT example SQL does not match its output (version-3.x/2.1)

[boluor]

On the GROUP_ARRAY_INTERSECT page (aggregate-functions/group-array-intersect.md, version-3.x and version-2.1), the first example does not match its own output:

select c_array_string from group_array_intersect_test where id in (18, 20);

+------+---------------------------+
| id   | col                       |
+------+---------------------------+
|    1 | ["a", "b", "c", "d", "e"] |
|    2 | ["a", "b"]                |
|    3 | ["a", null]               |
+------+---------------------------+

The SQL selects a single column c_array_string with predicate id IN (18, 20), but the shown output has columns id | col and rows with id = 1, 2, 3 (which contradicts the IN (18, 20) filter). The SQL and the displayed result are inconsistent.

Suggested fix — make the SQL match the shown two-column output and rows, e.g.:

select id, col from group_array_intersect_test;

(The second example, select group_array_intersect(col) from group_array_intersect_test; → ["a"], is consistent and fine.)

Filing this separately so the example-SQL correction can be reviewed on its own; the missing CREATE TABLE setup for these pages is being handled in the Line-B setup PRs.

[zclllyybb]

Breakwater-GitHub-Analysis-Slot: slot_68982604d84b

I checked the live issue and the current apache/doris-website source. The report looks valid and is a documentation consistency issue, not a Doris runtime issue.

In the English versioned docs, both affected files contain the same mismatch:

• versioned_docs/version-2.1/sql-manual/sql-functions/aggregate-functions/group-array-intersect.md
• versioned_docs/version-3.x/sql-manual/sql-functions/aggregate-functions/group-array-intersect.md

The first example runs:

select c_array_string from group_array_intersect_test where id in (18, 20);

but the displayed result is a two-column id | col table with rows 1, 2, and 3. That output cannot come from the shown SQL because the select list, column name, and filter all disagree with the result table.

The suggested narrow fix is reasonable if the 2.1/3.x setup PRs keep the old example schema with a column named col:

select id, col from group_array_intersect_test;

That would make the first example match its displayed output and keep the second example, select group_array_intersect(col) from group_array_intersect_test;, internally consistent.

One scope note: the same stale snippet also exists in the zh-CN and ja versioned copies for 2.1 and 3.x. If the docs PR updates localized snapshots directly, those copies should be aligned as well; otherwise they can follow the normal localization sync process.

No query logs, profiles, or Doris version-specific runtime evidence are needed to confirm this issue. The only thing to decide before merging a patch is the canonical example schema for these older pages: keep the old col schema and apply the narrow SQL correction above, or backport the current/4.x style setup that uses c_array_string throughout.