Fixed an issue that the SDK unnecessarily bufferred the entire conten…

[zoewangg]

…t for streaming operations

Motivation and Context

Fixed an issue that the SDK unnecessarily buffered the entire content for streaming operations. See
#5850

We changed RequestBody#fromContenProvider to buffer content in 9523cf5#diff-1a88bd363dd55e33ebf3734f8a96c524d600b3f46745c82169482718d43c030a commit. It was released in 2.30.9.

The root cause is that we are calling RequestBody#fromContenProvider in BaseClientHandler within the SDK to wrap the inputstream with SdkLengthAwareInputStream, which means all streams with known content length will be buffered.

Modifications

Create an internal class to extend RequestBody that just uses the contentStreamProvider as-is (instead of buffering).

Testing

Tested with customer's repro code and verified oom is no longer thrown

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud