Repository navigation
Conversation
csj4032
force-pushed
the
minor-typo-fixes-comments
branch
from
July 20, 2026 09:17
137d4e1 to
02ba242
Compare
csj4032
force-pushed
the
minor-typo-fixes-comments
branch
from
July 30, 2026 01:17
02ba242 to
6076c57
Compare
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
csj4032
force-pushed
the
minor-typo-fixes-comments
branch
from
October 14, 2026 04:21
6076c57 to
31aa66c
Compare
Author
|
Rebased onto the latest master to resolve the merge conflict. The typo fixes in cc @dongjoon-hyun @LuciferYang @HyukjinKwon — would you mind taking a look when you have a moment? Thank you. |
This branch has not been deployed
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
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.
What changes were proposed in this pull request?
Fix typos and minor grammar errors in code comments, docstrings, and one test name across 14 files: 19 misspellings plus one duplicated word, for 20 changed lines. No identifier, API, or behavior changes.
Typos fixed:
arbitaryarbitraryoverridenoverriddendependantdependentsplittedsplitpropogatepropagateneccessarynecessaryarguementargumentwritenwrittenseperateseparateAdjacent grammar issues found during the same scan were fixed as well:
should overriden->should be overridden(Client.scala)will splitted->will be split(TableReader.scala)thespanning two lines (DAGScheduler.scala) -- this is the 20th changed line, on top of the 19 misspellings aboveOne note on the diff, so it is easy to follow:
@param confsToOverrideline inClient.scalaexceeds the 100-character limit onceoverridenbecomesbe overridden, so it is wrapped onto two lines. This is why the diff is +21/-20 rather than +20/-20.Identifiers and public API names are deliberately left alone. For example
AbstractFileRegion.transfered()andDataWritingCommand.propogateMetrics()carry the same misspelling but are method names, so renaming them is out of scope for a[MINOR][DOCS]change.Why are the changes needed?
To improve readability and correctness of code comments and docstrings. Some of the fixes are in user-visible API docstrings (e.g.
pyspark.pandasgeneric.py/groupby.py), wherearbitaryappears in rendered documentation.Does this PR introduce any user-facing change?
No. Documentation/comment-only changes. The only rendered-output difference is the corrected spelling in the pandas-on-Spark docstrings noted above.
How was this patch tested?
No behavior change; existing CI.
Locally verified before pushing:
build/sbt -Pyarn -Pdocker-integration-testscompile plusscalastyleforcore,catalyst,sql,hive,yarn,catalyst/Testanddocker-integration-tests/Test-- 0 errors, 0 warnings.ruff checkandruff format --checkon the four changed Python files -- clean.The only non-comment edit is a test name in
CodeGenerationSuite.scala(splitted->split), covered by the existing suite.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 4.8, Claude Opus 5)