zclllyybb commented on issue #3905: URL: https://github.com/apache/doris-website/issues/3905#issuecomment-4610202509
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. -- 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]
