shangxinli opened a new pull request, #18763:
URL: https://github.com/apache/hudi/pull/18763

   ### Describe the issue this Pull Request addresses
   
   This is a minor cleanup PR. While reading through the codebase I noticed a 
handful of long-standing English typos in code comments and test assertion 
messages (`atleast`, `commited`, `existance`, `transfering`, `succesfully`). 
They don't affect behavior but reduce readability and surface in IDE 
spellcheckers and code search.
   
   ### Summary and Changelog
   
   Corrects 12 typo occurrences across 11 files. All changes are confined to 
comments and assertion-message string literals — no identifiers, configs, 
public APIs, or runtime behavior are touched.
   
   - `atleast` → `at least` (8 occurrences across `LazyIterableIterator`, 
`TestCoalescingPartitioner`, `CompactionTestBase` x2, 
`GenericRecordPartialPayloadGenerator`, `TestFileDeltaInputWriter`, 
`TestHoodieDeltaStreamerWithMultiWriter`)
   - `commited` → `committed` (1 occurrence in a comment in 
`HoodieBackedTableMetadataWriter`)
   - `existance` → `existence` (1 occurrence in an exception message in 
`TestHoodieSparkTable`)
   - `transfering` → `transferring` (2 occurrences in comments in 
`Spark41LegacyHoodieParquetFileFormat` and `Spark41ParquetReader`)
   - `succesfully` → `successfully` (1 occurrence in a comment in 
`scripts/pr_compliance.py`)
   
   ### Impact
   
   None. Comment-only and assertion-message string changes; no public API, 
config, storage format, or behavioral changes.
   
   ### Risk Level
   
   none
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable


-- 
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]

Reply via email to