# Stripped down elasticsearch client jar **URL:** \ **Category:** Elasticsearch\ **Created:** [April 11, 2011, 5:57pm UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215 "2011-04-11T17:57:22Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [April 11, 2011, 5:57pm UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/1 "2011-04-11T17:57:22Z")
Hi Shay, ``` Currently, the elasticsearch jar is ~11MB and I don't believe that ``` everything is necessary if using it for a stateless client. If this is true, you would mind creating an stripped down elasticsearch-client jar? Regards, Thiago Souza ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 11, 2011, 6:02pm UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/2 "2011-04-11T18:02:14Z")
When using transport client, then yes, it could be stripped, but its going to involve a lot of effort (and not sure how much it will save), so its not planned. On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > Hi Shay, > > Currently, the elasticsearch jar is ~11MB and I don't believe that everything is necessary if using it for a stateless client. > If this is true, you would mind creating an stripped down elasticsearch-client jar? > > Regards, > Thiago Souza ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [April 11, 2011, 6:24pm UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/3 "2011-04-11T18:24:52Z")
Ok, thanks... On Mon, Apr 11, 2011 at 15:02, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > When using transport client, then yes, it could be stripped, but its > going to involve a lot of effort (and not sure how much it will save), so > its not planned. > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > Hi Shay, > > ``` > Currently, the elasticsearch jar is ~11MB and I don't believe that > > ``` > > everything is necessary if using it for a stateless client. > If this is true, you would mind creating an stripped down > elasticsearch-client jar? > > Regards, > Thiago Souza ---
**Author:** ![Barsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barsk/32/13734_2.png) [@Barsk](https://discuss.elastic.co/u/Barsk)\ **Post date:** [April 12, 2011, 9:43am UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/4 "2011-04-12T09:43:14Z")
``` Hi, I understand the implications of isolating the client stuff in its own distro. But it would be quite nice if it could be done nevertheless. I use the client in a servlet container for a webapp and it gets rather messy to update a webapp to the lastest ES version since there are quite a few supporting jars that need to go in there to. Some of these jars are version-colliding with some of the jars I have put in so I end up having to upgrade my webapp stuff with new versions of the supporting jars (like logging etc etc). I even end up with Lucene jars in my webapp and that seems over the edge for a client. I guees some of these "supporting" jars are not really needed for the client, and this complexity could be reduced if there was a separate client distro. I use the native client, not the transport one. /Kristian Shay Banon skrev 2011-04-11 20:02:
When using transport client, then yes, it could be stripped, but its going to involve a lot of effort (and not sure how much it will save), so its not planned. ``` On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > Hi Shay, > >    Currently, the elasticsearch jar is ~11MB > and I don't believe that everything is necessary if > using it for a stateless client.   If this is true, you would mind creating an > stripped down elasticsearch-client jar? > > Regards,Thiago Souza ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 12, 2011, 9:45am UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/5 "2011-04-12T09:45:49Z")
Which supporting jars do you need for elasticsearch? Aside from the Lucene jars, which are needed only when using the NodeClient and not TransportClient, elasticsearch has no dependencies (the ones it uses are jarjar'ed into elasticsearch, like guice, jackson, and netty). On Tuesday, April 12, 2011 at 12:43 PM, Kristian Jörg wrote: > Hi, > > I understand the implications of isolating the client stuff in its own distro. But it would be quite nice if it could be done nevertheless. > I use the client in a servlet container for a webapp and it gets rather messy to update a webapp to the lastest ES version since there are quite a few supporting jars that need to go in there to. Some of these jars are version-colliding with some of the jars I have put in so I end up having to upgrade my webapp stuff with new versions of the supporting jars (like logging etc etc). I even end up with Lucene jars in my webapp and that seems over the edge for a client. > > I guees some of these "supporting" jars are not really needed for the client, and this complexity could be reduced if there was a separate client distro. > I use the native client, not the transport one. > > /Kristian > > Shay Banon skrev 2011-04-11 20:02: > > > When using transport client, then yes, it could be stripped, but its going to involve a lot of effort (and not sure how much it will save), so its not planned. > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > > > > Hi Shay, > > > > > > Currently, the elasticsearch jar is ~11MB and I don't believe that everything is necessary if using it for a stateless client. > > > If this is true, you would mind creating an stripped down elasticsearch-client jar? > > > > > > Regards, > > > Thiago Souza ---
**Author:** ![Barsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barsk/32/13734_2.png) [@Barsk](https://discuss.elastic.co/u/Barsk)\ **Post date:** [April 12, 2011, 1:06pm UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/6 "2011-04-12T13:06:40Z")
``` Well, that was the problem. I did not know which to use and which not to. My first tries failed, so to avoid a long trial-and-error I threw them all in. This is where improvements could be done. If all that is needed for the NodeClient is the easticsearch jar and the lucene jars, then a simple doc entry for that would help a lot. Mayby it is there, but it eluded me at least. Another question, if using only one instance of ES on localhost. Are there any drawbacks of using TransportClient? There was this mention of a double hop that I wanted to avoid. But maybe I can simplify my client setup... Shay Banon skrev 2011-04-12 11:45:
Which supporting jars do you need for elasticsearch? Aside from the Lucene jars, which are needed only when using the NodeClient and not TransportClient, elasticsearch has no dependencies (the ones it uses are jarjar'ed into elasticsearch, like guice, jackson, and netty). ``` On Tuesday, April 12, 2011 at 12:43 PM, Kristian Jörg wrote: > Hi, > > ``` > I understand the implications of isolating the client > stuff in its own distro. But it would be quite nice if > it could be done nevertheless. > > I use the client in a servlet container for a webapp > and it gets rather messy to update a webapp to the > lastest ES version since there are quite a few > supporting jars that need to go in there to. Some of > these jars are version-colliding with some of the jars > I have put in so I end up having to upgrade my webapp > stuff with new versions of the supporting jars (like > logging etc etc). I even end up with Lucene jars in my > webapp and that seems over the edge for a client. > > I guees some of these "supporting" jars are not really > needed for the client, and this complexity could be > reduced if there was a separate client distro. > > I use the native client, not the transport one. > > /Kristian > > Shay Banon skrev 2011-04-11 20:02: >
When using transport client, then > yes, it could be stripped, but its going to > involve a lot of effort (and not sure how > much it will save), so its not planned. > > ``` > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > > Hi Shay, > > > >    Currently, the > > elasticsearch jar is ~11MB and I > > don't believe that everything is > > necessary if using it for a > > stateless client.   If this is true, you > > would mind creating an stripped > > down elasticsearch-client jar? > > > > Regards,Thiago Souza ``` -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post:[kristian.jorg@devo.se](mailto:kristian.jorg@devo.se)Webb:[http://www.devo.se](http://www.devo.se) ``` ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 12, 2011, 1:17pm UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/7 "2011-04-12T13:17:22Z")
Its not doc'ed except for the maven pom definition, seems like most people use maven these days, no? On Tuesday, April 12, 2011 at 4:06 PM, Kristian Jörg wrote: > Well, that was the problem. I did not know which to use and which not to. My first tries failed, so to avoid a long trial-and-error I threw them all in. > This is where improvements could be done. If all that is needed for the NodeClient is the easticsearch jar and the lucene jars, then a simple doc entry for that would help a lot. Mayby it is there, but it eluded me at least. > > Another question, if using only one instance of ES on localhost. Are there any drawbacks of using TransportClient? There was this mention of a double hop that I wanted to avoid. But maybe I can simplify my client setup... > > Shay Banon skrev 2011-04-12 11:45: > > > Which supporting jars do you need for elasticsearch? Aside from the Lucene jars, which are needed only when using the NodeClient and not TransportClient, elasticsearch has no dependencies (the ones it uses are jarjar'ed into elasticsearch, like guice, jackson, and netty). > > On Tuesday, April 12, 2011 at 12:43 PM, Kristian Jörg wrote: > > > > > Hi, > > > > > > I understand the implications of isolating the client stuff in its own distro. But it would be quite nice if it could be done nevertheless. > > > I use the client in a servlet container for a webapp and it gets rather messy to update a webapp to the lastest ES version since there are quite a few supporting jars that need to go in there to. Some of these jars are version-colliding with some of the jars I have put in so I end up having to upgrade my webapp stuff with new versions of the supporting jars (like logging etc etc). I even end up with Lucene jars in my webapp and that seems over the edge for a client. > > > > > > I guees some of these "supporting" jars are not really needed for the client, and this complexity could be reduced if there was a separate client distro. > > > I use the native client, not the transport one. > > > > > > /Kristian > > > > > > Shay Banon skrev 2011-04-11 20:02: > > > > > > > When using transport client, then yes, it could be stripped, but its going to involve a lot of effort (and not sure how much it will save), so its not planned. > > > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > > > > > > > > Hi Shay, > > > > > > > > > > Currently, the elasticsearch jar is ~11MB and I don't believe that everything is necessary if using it for a stateless client. > > > > > If this is true, you would mind creating an stripped down elasticsearch-client jar? > > > > > > > > > > Regards, > > > > > Thiago Souza > > -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post: kristian.jorg@devo.se Webb: [http://www.devo.se](http://www.devo.se) ---
**Author:** ![Barsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barsk/32/13734_2.png) [@Barsk](https://discuss.elastic.co/u/Barsk)\ **Post date:** [April 13, 2011, 8:11am UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/8 "2011-04-13T08:11:35Z")
``` Shay Banon skrev 2011-04-12 15:17:
Its not doc'ed except for the maven pom definition, seems like most people use maven these days, no? ``` Well, no. I am on my way there, but not there yet. ``` And there are so many other build methods available so I think that expecting all users to use a specific build tool is incorrect. ``` > On Tuesday, April 12, 2011 at 4:06 PM, Kristian Jörg wrote: > > > Well, that was the problem. I did not know which to use and which not to. My first tries failed, so to avoid a long trial-and-error I threw them all in. > > > > ``` > > This is where improvements could be done. If all that > > is needed for the NodeClient is the easticsearch jar > > and the lucene jars, then a simple doc entry for that > > would help a lot. Mayby it is there, but it eluded me > > at least. > > > > Another question, if using only one instance of ES on > > localhost. Are there any drawbacks of using > > TransportClient? There was this mention of a double > > hop that I wanted to avoid. But maybe I can simplify > > my client setup... > > > > Shay Banon skrev 2011-04-12 11:45: > >
Which supporting jars do you need > > for elasticsearch? Aside from the Lucene > > jars, which are needed only when using the > > NodeClient and not TransportClient, > > elasticsearch has no dependencies (the ones > > it uses are jarjar'ed into elasticsearch, > > like guice, jackson, and netty). > > > > ``` > > > > On Tuesday, April 12, 2011 at 12:43 PM, Kristian Jörg wrote: > > > > > Hi, > > > > > > ``` > > > I understand the implications of > > > isolating the client stuff in its > > > own distro. But it would be quite > > > nice if it could be done > > > nevertheless. > > > > > > I use the client in a servlet > > > container for a webapp and it gets > > > rather messy to update a webapp to > > > the lastest ES version since there > > > are quite a few supporting jars that > > > need to go in there to. Some of > > > these jars are version-colliding > > > with some of the jars I have put in > > > so I end up having to upgrade my > > > webapp stuff with new versions of > > > the supporting jars (like logging > > > etc etc). I even end up with Lucene > > > jars in my webapp and that seems > > > over the edge for a client. > > > > > > I guees some of these "supporting" > > > jars are not really needed for the > > > client, and this complexity could be > > > reduced if there was a separate > > > client distro. > > > > > > I use the native client, not the > > > transport one. > > > > > > /Kristian > > > > > > Shay Banon skrev 2011-04-11 20:02: > > >
When using > > > transport client, then > > > yes, it could be > > > stripped, but its going > > > to involve a lot of > > > effort (and not sure how > > > much it will save), so > > > its not planned. > > > > > > ``` > > > > > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > > > > > > Hi Shay, > > > > > > > >    > > > > Currently, the > > > > elasticsearch > > > > jar is ~11MB > > > > and I don't > > > > believe that > > > > everything is > > > > necessary if > > > > using it for a > > > > stateless > > > > client.   If > > > > this is true, > > > > you would mind > > > > creating an > > > > stripped down > > > > elasticsearch-client > > > > jar? > > > > > > > > Regards,Thiago > > > > Souza ``` -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post:[kristian.jorg@devo.se](mailto:kristian.jorg@devo.se)Webb:[http://www.devo.se](http://www.devo.se) ``` ``` -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post:[kristian.jorg@devo.se](mailto:kristian.jorg@devo.se)Webb:[http://www.devo.se](http://www.devo.se) ``` ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 13, 2011, 8:12am UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/9 "2011-04-13T08:12:46Z")
ok, no problem to doc it. On Wednesday, April 13, 2011 at 11:11 AM, Kristian Jörg wrote: > Shay Banon skrev 2011-04-12 15:17: > > > Its not doc'ed except for the maven pom definition, seems like most people use maven these days, no? > > Well, no. I am on my way there, but not there yet. > > And there are so many other build methods available so I think that expecting all users to use a specific build tool is incorrect. > > On Tuesday, April 12, 2011 at 4:06 PM, Kristian Jörg wrote: > > > > > Well, that was the problem. I did not know which to use and which not to. My first tries failed, so to avoid a long trial-and-error I threw them all in. > > > This is where improvements could be done. If all that is needed for the NodeClient is the easticsearch jar and the lucene jars, then a simple doc entry for that would help a lot. Mayby it is there, but it eluded me at least. > > > > > > Another question, if using only one instance of ES on localhost. Are there any drawbacks of using TransportClient? There was this mention of a double hop that I wanted to avoid. But maybe I can simplify my client setup... > > > > > > Shay Banon skrev 2011-04-12 11:45: > > > > > > > Which supporting jars do you need for elasticsearch? Aside from the Lucene jars, which are needed only when using the NodeClient and not TransportClient, elasticsearch has no dependencies (the ones it uses are jarjar'ed into elasticsearch, like guice, jackson, and netty). > > > > On Tuesday, April 12, 2011 at 12:43 PM, Kristian Jörg wrote: > > > > > > > > > Hi, > > > > > > > > > > I understand the implications of isolating the client stuff in its own distro. But it would be quite nice if it could be done nevertheless. > > > > > I use the client in a servlet container for a webapp and it gets rather messy to update a webapp to the lastest ES version since there are quite a few supporting jars that need to go in there to. Some of these jars are version-colliding with some of the jars I have put in so I end up having to upgrade my webapp stuff with new versions of the supporting jars (like logging etc etc). I even end up with Lucene jars in my webapp and that seems over the edge for a client. > > > > > > > > > > I guees some of these "supporting" jars are not really needed for the client, and this complexity could be reduced if there was a separate client distro. > > > > > I use the native client, not the transport one. > > > > > > > > > > /Kristian > > > > > > > > > > Shay Banon skrev 2011-04-11 20:02: > > > > > > > > > > > When using transport client, then yes, it could be stripped, but its going to involve a lot of effort (and not sure how much it will save), so its not planned. > > > > > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > > > > > > > > > > > > Hi Shay, > > > > > > > > > > > > > > Currently, the elasticsearch jar is ~11MB and I don't believe that everything is necessary if using it for a stateless client. > > > > > > > If this is true, you would mind creating an stripped down elasticsearch-client jar? > > > > > > > > > > > > > > Regards, > > > > > > > Thiago Souza > > > > > > -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post: kristian.jorg@devo.se Webb: [http://www.devo.se](http://www.devo.se) > > -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post: kristian.jorg@devo.se Webb: [http://www.devo.se](http://www.devo.se) ---
**Author:** ![Barsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barsk/32/13734_2.png) [@Barsk](https://discuss.elastic.co/u/Barsk)\ **Post date:** [April 13, 2011, 9:45am UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/10 "2011-04-13T09:45:44Z")
``` Much appreciated! Shay Banon skrev 2011-04-13 10:12:
``` ok, no problem to doc it. On Wednesday, April 13, 2011 at 11:11 AM, Kristian Jörg wrote: > Shay Banon skrev 2011-04-12 15:17: > > > Its not doc'ed except for the maven pom definition, seems like most people use maven these days, no? > > Well, no. I am on my way there, but not there yet. > > ``` > And there are so many other build methods available so > I think that expecting all users to use a specific > build tool is incorrect. > > ``` > > > On Tuesday, April 12, 2011 at 4:06 PM, Kristian Jörg wrote: > > > > > Well, that was the problem. I did not know which to use and which not to. My first tries failed, so to avoid a long trial-and-error I threw them all in. > > > > > > ``` > > > This is where improvements could be > > > done. If all that is needed for the > > > NodeClient is the easticsearch jar > > > and the lucene jars, then a simple > > > doc entry for that would help a lot. > > > Mayby it is there, but it eluded me > > > at least. > > > > > > Another question, if using only one > > > instance of ES on localhost. Are > > > there any drawbacks of using > > > TransportClient? There was this > > > mention of a double hop that I > > > wanted to avoid. But maybe I can > > > simplify my client setup... > > > > > > Shay Banon skrev 2011-04-12 11:45: > > >
Which > > > supporting jars do you > > > need for elasticsearch? > > > Aside from the Lucene > > > jars, which are needed > > > only when using the > > > NodeClient and not > > > TransportClient, > > > elasticsearch has no > > > dependencies (the ones > > > it uses are jarjar'ed > > > into elasticsearch, like > > > guice, jackson, and > > > netty). > > > > > > ``` > > > > > > On Tuesday, April 12, 2011 at 12:43 PM, Kristian Jörg wrote: > > > > > > > Hi, > > > > > > > > ``` > > > > I understand > > > > the > > > > implications > > > > of isolating > > > > the client > > > > stuff in its > > > > own distro. > > > > But it would > > > > be quite nice > > > > if it could be > > > > done > > > > nevertheless. > > > > > > > > I use the > > > > client in a > > > > servlet > > > > container for > > > > a webapp and > > > > it gets rather > > > > messy to > > > > update a > > > > webapp to the > > > > lastest ES > > > > version since > > > > there are > > > > quite a few > > > > supporting > > > > jars that need > > > > to go in there > > > > to. Some of > > > > these jars are > > > > version-colliding > > > > > > > > with some of > > > > the jars I > > > > have put in so > > > > I end up > > > > having to > > > > upgrade my > > > > webapp stuff > > > > with new > > > > versions of > > > > the supporting > > > > jars (like > > > > logging etc > > > > etc). I even > > > > end up with > > > > Lucene jars in > > > > my webapp and > > > > that seems > > > > over the edge > > > > for a client. > > > > > > > > I guees some > > > > of these > > > > "supporting" > > > > jars are not > > > > really needed > > > > for the > > > > client, and > > > > this > > > > complexity > > > > could be > > > > reduced if > > > > there was a > > > > separate > > > > client distro. > > > > > > > > I use the > > > > native client, > > > > not the > > > > transport one. > > > > > > > > /Kristian > > > > > > > > Shay Banon > > > > skrev > > > > 2011-04-11 > > > > 20:02: > > > >
When > > > > using > > > > transport > > > > client, then > > > > yes, it could > > > > be stripped, > > > > but its going > > > > to involve a > > > > lot of effort > > > > (and not sure > > > > how much it > > > > will save), so > > > > its not > > > > planned. > > > > > > > > ``` > > > > > > > > On Monday, April 11, 2011 at 8:57 PM, Thiago Souza wrote: > > > > > > > > > Hi Shay, > > > > > > > > > >    > > > > > Currently, the > > > > > elasticsearch > > > > > jar is ~11MB > > > > > and I don't > > > > > believe that > > > > > everything is > > > > > necessary if > > > > > using it for a > > > > > stateless > > > > > client.   If > > > > > this is true, > > > > > you would mind > > > > > creating an > > > > > stripped down > > > > > elasticsearch-client > > > > > > > > > > ``` > > > > > jar? > > > > > > > > > > ``` > > > > > > > > > > Regards,Thiago > > > > > Souza > > ``` > -- > Med vänlig hälsning > Kristian Jörg > > Devo IT AB > Tel: 054 - 22 14 58, 0709 - 15 83 42 > E-post:[kristian.jorg@devo.se](mailto:kristian.jorg@devo.se)Webb:[http://www.devo.se](http://www.devo.se) > ``` ``` -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post:[kristian.jorg@devo.se](mailto:kristian.jorg@devo.se)Webb:[http://www.devo.se](http://www.devo.se) ``` ``` -- Med vänlig hälsning Kristian Jörg Devo IT AB Tel: 054 - 22 14 58, 0709 - 15 83 42 E-post:[kristian.jorg@devo.se](mailto:kristian.jorg@devo.se)Webb:[http://www.devo.se](http://www.devo.se) ``` ---
**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, 4:08am UTC](https://discuss.elastic.co/t/stripped-down-elasticsearch-client-jar/4215/11 "2017-07-06T04:08:25Z")