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.

Sign up for GitHub

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

Jump to bottom

Why would one use fesen-httpclient over org.opensearch.* client? #1

Open
dblock opened this issue Feb 7, 2022 · 1 comment
Open

Why would one use fesen-httpclient over org.opensearch.* client? #1

dblock opened this issue Feb 7, 2022 · 1 comment
Labels
question Further information is requested

Comments

@dblock
Copy link

dblock commented Feb 7, 2022

This is a very interesting project!

I can see that fesen-httpclient works with a broad(er) range of Elasticseaerch and OpenSearch. Is there any other reason to use this client over the native one? Either way I think the README could benefit from an FAQ.
@marevol
Copy link
Contributor

marevol commented Feb 7, 2022

This library is a part of Fess project.
Fess used TransportClient API before the native HTTP client was released, and it needed to use the same API on HTTP to access Elasticsearch.
So, this library was created before the native one and was refactored as fesen-httpclient.

@marevol marevol added the question Further information is requested label Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dblock @marevol