-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Migrate client transports to Apache HttpClient / Core 5.x #4256
Comments
@dblock @nknize @adnapibar any concerns / objections / risks? thanks! |
I wonder whether our time is better spent deleting the client-side components from this repo and moving them into a separate component as legacy without this upgrade? |
Feasible, but what will we offer as a client component replacement? |
I mean we need to decouple server from client. Users that want to talk to a server would consume opensearch-java which should contain everything it needs to talk to OpenSearch. And users that want to build extensions would consume opensearch-sdk-java. So maybe we should move REST clients into opensearch-java now (and delete all redundant parts)? |
Ah, sure, we could explore this path, but underlying transport (low level HTTP client) needs to be updated anyway, I think those two tracks could go in parallel. |
I was just trying to explore ways where less work can be done, or we can divide and conquer. |
@reta just read up your PR upgrading to Core 5.x. |
@saratvemulapalli sorry if I misinterpreted your question, the Rest Client and RHLC (Rest High Level Client) and https://github.com/Opensearch-project/Opensearch-java use Apache HttpClient under the hood. Now, different projects and application use either RHLC or |
Thanks @reta I understand the first part. My question is tangential to this upgrade, I completely agree it makes sense to upgrade HttpClient. My question mainly was, do customers use RHLC, why dont they use [1] https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-high.html |
Yeah, |
Sounds like it needs more discussion, i'll open an issue. |
@saratvemulapalli correct, |
Is your feature request related to a problem? Please describe.
All OpenSearch clients (rest-client., RHLC, opensearch-java) use Apache HttpComponents / Core 4.x, which are already EOLed and superseded by Apache HttpClient / Core 5.x. The migration to the Apache HttpClient / Core 5.x is a necessary undertaking (not only to benefit from HTTP/2 support but also to rely on maintanable libraries).
Describe the solution you'd like
Migrate client transports to Apache HttpClient / Core 5.x
Describe alternatives you've considered
Stay on Apache HttpComponents / Core 4.x
Additional context
See please #4257
The text was updated successfully, but these errors were encountered: