[fix] correct typo and wrong column name in two docs#3675
Merged
Conversation
- doris-onelake.md: removed a doubled word ("and and" -> "and").
- window-functions/overview.md: the prose referenced `ORDER BY dateid`,
but the example table test_window_order has no `dateid` column — its
sorting column is `date_time` (used by the example query and result).
Corrected the prose to `ORDER BY date_time`.
Applied across all affected EN and Chinese versions.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two small doc fixes (audit findings #8 and #9):
lakehouse/best-practices/doris-onelake.md: removed a doubled word ("...environment - and and explore..." → "...and explore...").sql-functions/window-functions/overview.md: the prose said the example fails "becauseORDER BY dateiddoes not provide a unique ordering", but the example tabletest_window_orderhas nodateidcolumn — its sorting column isdate_time(used by the example query and confirmed by the following line "the sorting columndate_time"). Corrected the prose toORDER BY date_time.Applied across all affected versions — onelake: EN next + 3.x/4.x; window overview: EN next + 4.x and ZH next + 4.x. (Other versions were already fine.)
Test plan
test_window_orderdefinesdate_time, notdateid