-
Notifications
You must be signed in to change notification settings - Fork 550
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
0.40.2 still not compatible with elasticsearch-cloud-aws plugin #995
Comments
Te reason for this issue is still the same as it was reported for crate 0.28.X: http://stackoverflow.com/questions/22321309/crate-0-28-0-1-and-elasticsearch-cloud-aws-plugin-compatibility Elasticsearch makes extensive use of shading (see http://maven.apache.org/plugins/maven-shade-plugin/ and https://github.com/elasticsearch/elasticsearch/blob/v1.3.0/pom.xml#L665) That is, bundling dependencies under another namespace ( The referenced It is a pitty, and I'm really sorry for that, but we currently don't have the time to dig into all the possibly useful elasticsearch plugins to make them usable with crate. But, naturally, we would appreciate any engagement. |
I understand. Thank you for the explanation. Our use-case is primarily for availability zone awareness. And we've been able to accomplish that by simply using the AWS api in our startup scripts. |
Oh, good to hear that you found a workaround! :) |
@mfelsche has this changed since then? Really looking forward to add Kubernetes discovery support. |
Unfortunately i have to say: not yet! |
This plugin is extremely useful and would be great for discovery and cluster allocation awareness.
cloud-aws 2.2.0 should be compatible w/ ES 1.2.2 used in Crate 0.40.2? https://github.com/elasticsearch/elasticsearch-cloud-aws/tree/es-1.2
The text was updated successfully, but these errors were encountered: