Closed essiembre closed 7 years ago
@niels, after checking with @pascaldimassimo, the latest (snapshot) version of Elasticsearch Committer now gives the option to use the Transport Client instead of the Node Client. That's not the same as using the REST API, but it is apparently the recommended usage when using the Node Client is not possible.
Because the option to use the Transport Client is now there, and it is more efficient than using the REST API (when using a Java client at least), we do not see advantages to also support the REST API. Do you?
In any case, I am quite grateful for your contribution and I decided to provide a link to it in a new Contributions page I just created
Thanks @essiembre!
The transport client is a good option to have but does not address the common use case of putting elasticsearch behind a HTTP proxy as it uses the proprietary elasticsearch transport protocol (rather than HTTP).
Putting ES behind an HTTP proxy is a popular way of i.a. adding encryption (HTTPS) and authentication (HTTP Basic Auth).
Agreed. I vote for basic capability of using the REST client.
For the latest versions, Elasticsearch announced that the java and transport APIs will soon be deprecated in favour of the REST client. So it might be necessary at some point to promote the client contributed by @niels
Hi @pascaldimassimo! A REST version is now in the work to replace the transport one, taking inspiration from @niels and @danizen. It should be available in the very near future. Thanks to all for your input.
Okay - I urge you to include HTTP basic authentication, similar code to what you do for Mongo, but just basic auth.
Done! Try the new snapshot release.
For usage, refer to Javadoc documentation for now until the site gets updated.
Given Elasticsearch decided to eventually stop supporting the transport client, I replaced it with the REST API. Those wanting to keep using the transport client will have to stick to version 3.
@danizen It does support basic authentication, but that's the only thing I did not get a chance to test.
Please give it a try and confirm.
I wanted to give feedback that this is working for me. I've removed my custom code and moved to the snapshot releases of collector-core, collector-http, and committer-elasticsearch. My project now contains no Java, which I will have to fix soon.
Can you confirm the authentication part as well?
Hi, first of all, thanx for the great job. When can we expect a release for this? Version 4 with REST support I mean. I can access only the official MVN repo and even the SNAPSHOT can not be found there. Thanx
Ask and you shall receive! I was waiting for @danizen to confirm the authentication part is working fine for him, but given the time, I am pretty sure it is. You can get the 4.0.0 release here. If you run into issues, please create a new ticket.
Great, hoping to see it soon in the mvn official repo too. thx
It is already deployed here: https://oss.sonatype.org/content/repositories/releases/com/norconex/collectors/norconex-committer-elasticsearch/4.0.0/
It may take up to a few hours for it gets propagated to Maven Central.
You are right. It takes time.
From @niels, in https://github.com/Norconex/collector-http/issues/200#issuecomment-168659138: