Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
transport client fails in uber jar - no shortHash #21627
Elasticsearch version: 5.0.1
Plugins installed: [ReindexPlugin, PercolatorPlugin, MustachePlugin, Netty3Plugin, Netty4Plugin, XPackPlugin]
JVM version: 1.8.0_112
OS version: osx 10.12.1
Description of the problem including expected versus actual behavior:
Getting the cluster node info fails when using the transport client from an uber jar.
Steps to reproduce:
Provide logs (if relevant):
Describe the feature:
Maybe get the build info from an elasticsearch specific file in the classpath, so it is more uber jar friendly.
You should create the jar using the
You must have the
I'm saying that if you tear our jar apart, you need to put it back together with all the pieces that we expect to be there (for example, having the manifest entires that we are looking for like you suggested previously).
You should at least update the docs to avoid this confusion in the future.
@csouthwell I think you're going to need to ask some Leiningen experts, the ES team doesn't have expertise in how to do things that we don't support, in a build tool that we don't support. Sorry.
My advice would be to hit stackoverflow (or a lein specific forum) and ask how to add specific entries to the manifest when running