freeformstu opened a new issue, #3127:
URL: https://github.com/apache/arrow-rs/issues/3127

   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   <!--
   A clear and concise description of what the problem is. Ex. I'm always 
frustrated when [...] 
   (This section helps Arrow developers understand the context and *why* for 
this feature, in addition to  the *what*)
   -->
   I am connecting to our Ceph cluster and getting intermittent connection 
closed errors from the server. I have tried both multipart and non-multipart 
uploads and have had the same issues.
   
   Others have run into this issue with the S3 API with reqwest/hyper and have 
needed to change their client configuration to resolve the issue.
   See:
   * https://github.com/hyperium/hyper/issues/2136
   * https://github.com/hyperium/hyper/issues/2136#issuecomment-861826148
   
   
   **Describe the solution you'd like**
   <!--
   A clear and concise description of what you want to happen.
   -->
   I would like to expose the reqwest client for custom configuration.
   
   **Describe alternatives you've considered**
   <!--
   A clear and concise description of any alternative solutions or features 
you've considered.
   -->
   An alternative would be to expose individual configuration settings in the 
Reqwest client and continue to shield creation of the client from the end user. 
This seems like unnecessary complexity for the object store to expose.
   
   Another alternative would be to make the reqwest client public so that it 
can be modified after the S3Client has been created. Exposing the client in 
this way is bad API design. Keeping the client private while allowing initial 
configuration seems to me to be the best route.
   
   **Additional context**
   <!--
   Add any other context or screenshots about the feature request here.
   -->
   


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