Too many Jar dependencies while using ES Transport client


(Kedar Dixit) #1

Hi,

I have been using ES Transport client in our product to fetch data from ES Server.

When I use below maven dependency and build the project:

<dependency>
	<groupId>org.elasticsearch.client</groupId>
	<artifactId>transport</artifactId>
	<version>5.4.3</version>
</dependency>

There are more than 30 jars that are getting shipped along with this jar.

Same is the case if I use ES-Spark connector where I see more than 100 jars being shipped.

What can be done for this one ? because shipping these many jars every time for new deployment is not a good practice.


(David Pilato) #2

May be this can help: https://www.elastic.co/blog/to-shade-or-not-to-shade


(Kedar Dixit) #3

Thanks but I need to solve issue of shipping too many jars along with my maven build. What can be done to ship only client jar ?


(David Pilato) #4

Shade your project. It will produce one single jar containing all classes.
You don't need to do any relocation. Just shade.

My 2 cents


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.