zclllyybb commented on issue #3889:
URL: https://github.com/apache/doris-website/issues/3889#issuecomment-4604588653
Breakwater-GitHub-Analysis-Slot: slot_3fa6174cd4c1
Initial analysis: this looks valid as a documentation bug, not a Doris
engine bug.
What I checked:
- The live issue has no labels and no comments yet.
- On refreshed `upstream/master` (`47bc039d5`), both
`versioned_docs/version-3.x/sql-manual/sql-functions/table-functions/explode-split.md`
and
`versioned_docs/version-2.1/sql-manual/sql-functions/table-functions/explode-split.md`
show `k2 = 1,2,3` for `k1 = 5`, then run `order by k1, e1`, but the expected
rows are shown as `2`, `3`, `1`.
- For this example, the returned `e1` values are single-character strings,
so `ORDER BY k1, e1` should sort them as `1`, `2`, `3`. That matches the
issue's reported verification on 3.1.4 and 2.1.11.
- PR #3890 is related but only adds the missing `example1` setup; it
explicitly leaves this output-order bug to #3889.
Recommended next step:
- Update the expected-output block to `1`, `2`, `3` in the two reported
English versioned docs files:
-
`versioned_docs/version-3.x/sql-manual/sql-functions/table-functions/explode-split.md`
-
`versioned_docs/version-2.1/sql-manual/sql-functions/table-functions/explode-split.md`
- To keep localized docs consistent, apply the same row-order correction to
the matching zh-CN and ja-source version-3.x/version-2.1 files.
- Optional sweep:
`versioned_docs/version-2.0/sql-manual/sql-functions/table-functions/explode-split.md`
and its zh-CN mirror appear to have the same unsorted block; `version-1.2`
already appears sorted.
Missing info:
- No additional runtime logs or profile are required to accept this as a
docs fix. If someone believes the engine can return `2`, `3`, `1` for the
displayed SQL, the useful extra evidence would be the exact table setup, Doris
build version, session variables, and raw query output.
--
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]
