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