# TransportClient and its limited libraries **URL:** \ **Category:** Elasticsearch\ **Created:** [August 21, 2012, 7:31am UTC](https://discuss.elastic.co/t/transportclient-and-its-limited-libraries/8796 "2012-08-21T07:31:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 21, 2012, 7:31am UTC](https://discuss.elastic.co/t/transportclient-and-its-limited-libraries/8796/1 "2012-08-21T07:31:27Z")
Hi there, as current elasticsearch allows one to use plugins in the transport client, i just tried with the fst plugin, but failed somewhat. I am getting tons of guice errors for missing implementations, among them - ClusterService - NodeService - IndicesService - FsProbe - NetworkProbe - ProcessProbe When looking at the initialization of the TransportClient it looks to me, that it is simply more lightweight than a node and does not start tons of services. What is the proposed solution for this? Should I split my fst suggester package in some client/serveer manner? Or am I doing something stupid when initializing my actions? The initializaton can be seen here [https://github.com/spinscale/elasticsearch-suggest-plugin/blob/master/src/main/java/org/elasticsearch/module/suggest/SuggestModule.java](https://github.com/spinscale/elasticsearch-suggest-plugin/blob/master/src/main/java/org/elasticsearch/module/suggest/SuggestModule.java) Thanks for any help! Regards, Alexander -- ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 21, 2012, 2:18pm UTC](https://discuss.elastic.co/t/transportclient-and-its-limited-libraries/8796/2 "2012-08-21T14:18:01Z")
Hi Alexander, TransportClient is now dependent on the Lucene jar(s) - I stumbled upon this before [CompressorFactory forces inclusion of lucene jars to TransportClient applications · Issue #2091 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2091) This might be the cause for the injection errors, but I'm not sure. Hopefully including the Lucene jars will fix the injection issues. Best regards, Jörg On Tuesday, August 21, 2012 9:31:27 AM UTC+2, Alexander Reelsen wrote: > Hi there, > > as current elasticsearch allows one to use plugins in the transport > client, i just tried with the fst plugin, but failed somewhat. > > I am getting tons of guice errors for missing implementations, among them > > - ClusterService > - NodeService > - IndicesService > - FsProbe > - NetworkProbe > - ProcessProbe > > When looking at the initialization of the TransportClient it looks to me, > that it is simply more lightweight than a node and does not start tons of > services. > > What is the proposed solution for this? Should I split my fst suggester > package in some client/serveer manner? Or am I doing something stupid when > initializing my actions? > The initializaton can be seen here > [https://github.com/spinscale/elasticsearch-suggest-plugin/blob/master/src/main/java/org/elasticsearch/module/suggest/SuggestModule.java](https://github.com/spinscale/elasticsearch-suggest-plugin/blob/master/src/main/java/org/elasticsearch/module/suggest/SuggestModule.java) > > Thanks for any help! > > Regards, Alexander -- ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 21, 2012, 3:24pm UTC](https://discuss.elastic.co/t/transportclient-and-its-limited-libraries/8796/3 "2012-08-21T15:24:48Z")
Hey Jörg, On Tue, Aug 21, 2012 at 4:18 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > TransportClient is now dependent on the Lucene jar(s) - I stumbled upon > this before [CompressorFactory forces inclusion of lucene jars to TransportClient applications · Issue #2091 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2091) > This might be the cause for the injection errors, but I'm not sure. > Hopefully including the Lucene jars will fix the injection issues. Nope, they were already included. Because of the Exception due to missing Probes I was thinking the sigar libs were missing, but as this happens when I try to add the (suggest) actions to the client (which of course does not need them as it is a client not a server) the problem occurs. --Alexander -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:15am UTC](https://discuss.elastic.co/t/transportclient-and-its-limited-libraries/8796/4 "2017-07-06T03:15:40Z")