luoyuan3471 opened a new pull request, #8868:
URL: https://github.com/apache/hadoop/pull/8868

   ### Description of PR
   
   Fixes [HADOOP-20039](https://issues.apache.org/jira/browse/HADOOP-20039).
   
   Correct two spelling mistakes in the fs.s3a.retry.throttle.interval 
description in core-default.xml:
   
   - "intial" to "initial".
   - "thundering heard" to "thundering herd".
   
   Only description text is changed. Configuration names and values, timing 
behavior, executable code, and existing end-of-file formatting are unchanged.
   
   ### How was this patch tested?
   
   git diff --check passed; core-default.xml parses successfully; all 
non-description property fields match the base; the entire file was compared to 
verify only the two intended word substitutions. No Maven build or unit tests 
were run locally. No new functional tests are needed for this 
documentation-only correction.
   
   If test4tests reports the absence of modified test files, please review that
   item as not applicable to this text-only patch. Actual build and test 
failures
   must still be evaluated separately.
   
   ### For code changes:
   
   - [x] The PR title starts with the corresponding JIRA issue id.
   - [ ] Object storage integration tests (not applicable; no object storage 
code changes).
   - [ ] Dependency licensing (not applicable; no new dependencies).
   - [ ] LICENSE, LICENSE-binary, or NOTICE-binary updates (not applicable).
   
   ### AI Tooling
   
   - [x] Contains content generated by Codex.
   - [x] My use of AI contributions follows the ASF legal policy:
     https://www.apache.org/legal/generative-tooling.html
   


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

Reply via email to