hesampakdaman opened a new pull request, #5806:
URL: https://github.com/apache/arrow-rs/pull/5806

   # Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   Closes #5396 
   
   # What changes are included in this PR?
   This PR introduces a new `RequestContext` struct that encapsulates the 
`RetryConfig` and a semaphore to limit the number of concurrent retry requests. 
This replaces the previous use of `RetryConfig` alone. The semaphore is used in 
the `send_retry` method. 
   
   - `RequestContext`: Combines `RetryConfig` and a semaphore.
   - Concurrency Control: Semaphore in `send_retry` limits simultaneous retry 
requests.
   - Client Update: Clients like `S3Client` now use `RequestContext` instead of 
`RetryConfig` in its `S3Config`.
   
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   
   # Are there any user-facing changes?
   
   All clients now use `RequestContext`, meaning all relevant new methods will 
require `RequestContext` instead of `RetryConfig`. This change impacts how 
clients are initialized and configured, necessitating updates to existing 
client initialization code.
   
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!---
   If there are any breaking changes to public APIs, please add the `breaking 
change` label.
   -->
   


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