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

[Elasticsearch] upgrade to version 5 #221

Closed
jnioche opened this Issue Nov 27, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@jnioche
Member

jnioche commented Nov 27, 2015

Amazon Elasticsearch does not support the native protocol and requires a REST based client like Jest. It would be good to have that as well

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Jul 8, 2016

Member

Elasticsearch 5 will provide

"a low-level Java HTTP/REST client. It provides a simple HTTP client with minimal dependencies, which handles sniffing, logging, round robinning of requests, and retry on node failure."

Member

jnioche commented Jul 8, 2016

Elasticsearch 5 will provide

"a low-level Java HTTP/REST client. It provides a simple HTTP client with minimal dependencies, which handles sniffing, logging, round robinning of requests, and retry on node failure."

@jnioche jnioche changed the title from [Elasticsearch] REST based client to [Elasticsearch] upgrade to version 5 Nov 1, 2016

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Feb 2, 2017

Member

Search-time field collapsing with paging is EXACTLY what we need for our spouts!

[https://www.elastic.co/guide/en/elasticsearch/reference/5.x/search-request-collapse.html] but won't be there until 5.3

Member

jnioche commented Feb 2, 2017

Search-time field collapsing with paging is EXACTLY what we need for our spouts!

[https://www.elastic.co/guide/en/elasticsearch/reference/5.x/search-request-collapse.html] but won't be there until 5.3

@jnioche jnioche self-assigned this Feb 2, 2017

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Feb 7, 2017

Member

Am having problems with the log dependencies which conflict with the ones in Storm

https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/_using_another_logger.html

Worth noticing that ES-Hadoop does not use the Java client (which causes the log dependency) but handles things through REST.

Member

jnioche commented Feb 7, 2017

Am having problems with the log dependencies which conflict with the ones in Storm

https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/_using_another_logger.html

Worth noticing that ES-Hadoop does not use the Java client (which causes the log dependency) but handles things through REST.

@kkrugler

This comment has been minimized.

Show comment
Hide comment
@kkrugler

kkrugler Feb 7, 2017

Elastic is pushing hard for everyone to transition to the REST client, versus the Java (Transport or Node) client.

kkrugler commented Feb 7, 2017

Elastic is pushing hard for everyone to transition to the REST client, versus the Java (Transport or Node) client.

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Mar 2, 2017

Member

Fixed the log dependency problem by updating the versions in Storm for the branches 1.0.x and 1.x. There is also an open PR for 2.x. Have used the branch es5 and it works great. Might wait for Elasticseach 5.3 to be released as it will contain the field collapsing mentioned earlier. Will open a sub-branch specifically for that and test the perfs vs using aggregations.

Member

jnioche commented Mar 2, 2017

Fixed the log dependency problem by updating the versions in Storm for the branches 1.0.x and 1.x. There is also an open PR for 2.x. Have used the branch es5 and it works great. Might wait for Elasticseach 5.3 to be released as it will contain the field collapsing mentioned earlier. Will open a sub-branch specifically for that and test the perfs vs using aggregations.

@jnioche jnioche added this to the 1.5 milestone Mar 29, 2017

@jnioche jnioche closed this in #451 Apr 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment