We had ElasticSearch with 1.4.2 and had code using TransportClient.
We are now trying to upgrade to ES 2.3.2 but I am facing several issues with the jar files.
This is the code used to connect to ES server using TransportClient
Settings settings = Settings.settingsBuilder()
.put( "cluster.name", OnedataProperties.ES_CLUSTER_NAME )
.put( "node.http.enabled", nodeHttpEnable ).put( "gateway.type", gatewaytype )
.put( "client.transport.sniff", transportSnif ).put( "index.store.type", indexStortype )
client = TransportClient.builder().settings( settings ).build();
( (TransportClient) client ).addTransportAddress( new InetSocketTransportAddress( InetAddress
.getByName( "XX.XX.XX.XX" ), 9300 ) );
With 1.4.2, I had included only lucene-core, lucene-analyzers-common, guava and elasticsearch jar files in my client application and it was working fine. After upgrade, I have upgraded the version of the 4 jar files to use the ones in sync with ES 2.3.2. However, when I run my application, it keeps throwing me dependency errors one by one - stating that it needs jsr166e-1.1.0.jar, t-digest-3.0.jar, netty.jar etc. The list is growing and seems endless.
Can you please let me know
Is there a thin client version of the ElasticSearch library that can be included in the client application?
What is the complete list of jar files that I need to include in my client application to work with ES 2.3.2?
I have used the default elasticsearch.yml file that comes with the installation. Are there any changes that need to be done in the yml file?