ApiClient: support deserializing from InputStream instead of String to bypass 2GB Java String limit #4021
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue #4020 .
Makes two changes:
ApiClient
, if we are deserializing JSON, get the response body as anInputStream
instead ofString
for deserialization.deserialize()
method inJSON.java
which acceptsInputStream
.These two changes enable the
ApiClient
to bypass the 2GBString
length limit in Java and deserialize large responses greater than 2GB into Java objects.