0.40.2 still not compatible with elasticsearch-cloud-aws plugin about crate

[mfelsche]

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 (org.elasticsearch.common) in their own jar. The elasticsearch-cloud-aws plugin has been programmed against the elasticsearch jar. We developed crate against the elasticsearch sources as we had to dig a little deeper and we needed to get rid of the shaded dependencies. Long story short, (vanilla) elasticsearch plugins programmed against the elasticsearch jar won't work with crate due to the shading.

The referenced org.elasticsearch.common.collect.Lists comes from googles guava.
One would have to fork the plugin and refactor all the dependencies to org.elasticsearch.common to point to their original sources.

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.

[jeffnappi]

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.

[mfelsche]

Oh, good to hear that you found a workaround! :)
We will keep this issue in mind. Meanwhile, I will close this issue.
Thanks! :)

[pires]

@mfelsche has this changed since then? Really looking forward to add Kubernetes discovery support.

[mfelsche]

Unfortunately i have to say: not yet!
But we still a solution for this on our backlog.
So stay tuned! :)