[doc] explode-bitmap (4.x/3.x/2.1): stray explode_json_object example references non-existent columns; dev already dropped it

[boluor]

On the EXPLODE_BITMAP page (sql-manual/sql-functions/table-functions/explode-bitmap.md) in version-4.x / version-3.x / version-2.1, the last example is a copy-paste error:

CREATE TABLE example ( k1 INT, v1 bitmap ) ... ;
insert into example values(1,to_bitmap('10101')),(2,to_bitmap('0')),(3,to_bitmap(NULL));

SELECT id, k, v
FROM example
LATERAL VIEW explode_json_object(value_json) exploded_table AS k , v;

• It calls explode_json_object(value_json), but example has no value_json column (only k1, v1), and selects id, k, v which don't exist either.
• The printed output (k1 / bit columns: 2→0, 1→10101) is actually the result of explode_bitmap(v1), not explode_json_object.
• On 2.1/3.x this fails (the AS k, v alias list is misparsed → Unknown table 'v').

The dev version of this page has already removed this broken block. Recommend aligning 4.x/3.x/2.1 with dev — either drop the stray example or rewrite it as a valid explode_bitmap(v1) example matching the shown output. Happy to send the PR.

[zclllyybb]

Breakwater-GitHub-Analysis-Slot: slot_a73147126f5f

Thanks for the report. I checked the current apache/doris-website master source and the published docs pages.

Confirmed for the English versioned_docs/version-3.x/sql-manual/sql-functions/table-functions/explode-bitmap.md and versioned_docs/version-2.1/sql-manual/sql-functions/table-functions/explode-bitmap.md: the tail examples create only k1 and v1, but then run explode_json_object(value_json) / explode_json_object_outer(value_json) and project id, k, v. The shown result tables use k1 / bit and match the preceding bitmap data, so these are copy-pasted JSON-object examples and should not remain on the EXPLODE_BITMAP page.

One scope clarification: current versioned_docs/version-4.x/.../explode-bitmap.md, current docs/.../explode-bitmap.md (dev), and the published 4.x/dev pages do not contain these stale blocks. I would treat the remaining source cleanup as 3.x and 2.1. The same stale blocks are also present in the zh-CN and ja versioned 3.x/2.1 copies, so a cleanup PR should consider those files too.

Recommended fix: align 3.x/2.1, and the localized versioned copies, with dev/4.x by removing both stray explode_json_object and explode_json_object_outer examples. If maintainers prefer to keep an additional bitmap example, it should be rewritten to use LATERAL VIEW explode_bitmap(v1) ... AS bit and only columns that exist in the created table.

Missing information: none needed for initial triage; this is reproducible directly from the docs source and the published 3.x/2.1 pages. No Doris code change appears required.