Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade async http client #345

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

cbrentharris
Copy link
Contributor

The project has moved to a new repo; please refer to apache/pinot#7968 and AsyncHttpClient/async-http-client#934 for motivation

Current usages of async http client when making SSL connections
is having issues. Upgrading the client, similar to pinot in this PR

apache/pinot#7968
Copy link

@aliciatang aliciatang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Comment on lines +22 to 27
public static synchronized AsyncHttpClient getAsyncHttpClient() {
if (_client.get() == null) {
initialize(new AsyncHttpClientConfig.Builder().build());
initialize(new Builder().build());
}
return _client.get();
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should instead introduce getAsyncHttpClient() alongside getNingClient() and mark getNingClient() as @Deprecated. I know the type has changed, and there's nothing we can do about that, but there are users of this code that will break if getNingClient() disappears on a minor version bump.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to confer with the team about the other breaking changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only concern I would have with that is if ning needs a different version of netty (or other) that the new project needs. What are your thoughts on that behavior? Would you like to see the dependency resolution for netty?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants