refactor: Use global http client to share the connection pool #16276
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.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
Utilize a global request client to share the connection pool. This change can prevent users from creating too many short-lived connections, which could exhaust the entire local port range in extreme cases.
NOTE: this is the default behavior of aws-sdk-sdk and we have already uses the same http client in our
DataOperator
. This change makes sure that all stage, external location table can use the same client.Tests
Type of change
This change is