# Separate ES library for search request?

**URL:** <https://discuss.elastic.co/t/separate-es-library-for-search-request/12552>\
**Category:** Elasticsearch\
**Created:** [June 26, 2013, 12:32pm UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552 "2013-06-26T12:32:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![amos\_wood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amos_wood/32/1880_2.png) [@amos\_wood](https://discuss.elastic.co/u/amos_wood)\
**Post date:** [June 26, 2013, 12:32pm UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552/1 "2013-06-26T12:32:33Z")

</div>

We have a need for many of our services to build ElasticSearch JSON search  
requests and pass them into a separate service's REST endpoint that is  
actually doing the searches. In order to build the searches, they are  
utilizing the QueryBuilder, FilterBuilder, and SearchRequestBuilder classes  
from the "org.elasticsearch.search" package. Currently, we have to include  
the whole, heavy-weight "elasticsearch-0.90.2.jar" and dependent libraries  
into quite a few services to make this work which is causing issues with a  
large number of loaded classes and such in our service servers. It would  
be desirable to have some of the packages in the "elasticsearch-\*.jar"  
files split into separate JAR files so that only the needed packages could  
be bundled into our WARs.

Does anyone know if this has been done already by a third-party?

Does anyone else have the same or similar needs so that this could be put  
on the to-be-developed list for ES?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [June 26, 2013, 2:42pm UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552/2 "2013-06-26T14:42:14Z")

</div>

First of all: 0.90.2 is released? No announcement, but it's on the download  
page. Issues were still being tagged 0.90.2 several hours ago.

There is no separate client library. Jorg was working on one, but I do not  
know the status:

> **[GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of...](https://github.com/jprante/elasticsearch-client)**
>
> Modularized, OpenJDK 11 version of Elasticsearch client - GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client

> **[GitHub - jprante/elasticsearch-helper: Helper classes for Elasticsearch client](https://github.com/jprante/elasticsearch-helper)**
>
> Helper classes for Elasticsearch client. Contribute to jprante/elasticsearch-helper development by creating an account on GitHub.

--  
Ivan

On Wed, Jun 26, 2013 at 5:32 AM, amos.wood [amos.wood@lifeway.com](mailto:amos.wood@lifeway.com) wrote:

> We have a need for many of our services to build Elasticsearch JSON search  
> requests and pass them into a separate service's REST endpoint that is  
> actually doing the searches. In order to build the searches, they are  
> utilizing the QueryBuilder, FilterBuilder, and SearchRequestBuilder classes  
> from the "org.elasticsearch.search" package. Currently, we have to include  
> the whole, heavy-weight "elasticsearch-0.90.2.jar" and dependent libraries  
> into quite a few services to make this work which is causing issues with a  
> large number of loaded classes and such in our service servers. It would  
> be desirable to have some of the packages in the "elasticsearch-\*.jar"  
> files split into separate JAR files so that only the needed packages could  
> be bundled into our WARs.
> 
> Does anyone know if this has been done already by a third-party?
> 
> Does anyone else have the same or similar needs so that this could be put  
> on the to-be-developed list for ES?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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:** [June 26, 2013, 4:16pm UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552/3 "2013-06-26T16:16:06Z")

</div>

I intend to continue the work on my Java "client only" ES version when  
ES 1.0 is feature complete, but if there is demand, I can pick up the  
development sooner.

Note, in order to create a smaller client library, not much code can be  
dropped, in fact, there are some Lucene jars which are not related to  
queries. Compression is a feature that could be dropped (or redesigned  
as optinal via META-INF/services) if a small client jar size is most  
important, but I have to check how Lucene supports this.

Jörg

Am 26.06.13 16:42, schrieb Ivan Brusic:

> First of all: 0.90.2 is released? No announcement, but it's on the  
> download page. Issues were still being tagged 0.90.2 several hours ago.
> 
> There is no separate client library. Jorg was working on one, but I do  
> not know the status:  
> [GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client](https://github.com/jprante/elasticsearch-client)  
> [GitHub - jprante/elasticsearch-helper: Helper classes for Elasticsearch client](https://github.com/jprante/elasticsearch-support)
> 
> --  
> Ivan
> 
> On Wed, Jun 26, 2013 at 5:32 AM, amos.wood \<[amos.wood@lifeway.com](mailto:amos.wood@lifeway.com)  
> [mailto:amos.wood@lifeway.com](mailto:amos.wood@lifeway.com)\> wrote:
> 
> ```
> We have a need for many of our services to build ElasticSearch
> JSON search requests and pass them into a separate service's REST
> endpoint that is actually doing the searches. In order to build
> the searches, they are utilizing the QueryBuilder, FilterBuilder,
> and SearchRequestBuilder classes from the
> "org.elasticsearch.search" package. Currently, we have to include
> the whole, heavy-weight "elasticsearch-0.90.2.jar" and dependent
> libraries into quite a few services to make this work which is
> causing issues with a large number of loaded classes and such in
> our service servers. It would be desirable to have some of the
> packages in the "elasticsearch-*.jar" files split into separate
> JAR files so that only the needed packages could be bundled into
> our WARs.
> 
> Does anyone know if this has been done already by a third-party?
> 
> Does anyone else have the same or similar needs so that this could
> be put on the to-be-developed list for ES?
> -- 
> You received this message because you are subscribed to the Google
> Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to elasticsearch+unsubscribe@googlegroups.com
> <mailto:elasticsearch%2Bunsubscribe@googlegroups.com>.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> ```
> 
> --  
> You received this message because you are subscribed to the Google  
> Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send  
> an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![amos\_wood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amos_wood/32/1880_2.png) [@amos\_wood](https://discuss.elastic.co/u/amos_wood)\
**Post date:** [June 27, 2013, 12:42pm UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552/4 "2013-06-27T12:42:36Z")

</div>

We definitely have a need for a "client only" library.

On Wednesday, June 26, 2013 11:16:06 AM UTC-5, Jörg Prante wrote:

> I intend to continue the work on my Java "client only" ES version when  
> ES 1.0 is feature complete, but if there is demand, I can pick up the  
> development sooner.
> 
> Note, in order to create a smaller client library, not much code can be  
> dropped, in fact, there are some Lucene jars which are not related to  
> queries. Compression is a feature that could be dropped (or redesigned  
> as optinal via META-INF/services) if a small client jar size is most  
> important, but I have to check how Lucene supports this.
> 
> Jörg
> 
> Am 26.06.13 16:42, schrieb Ivan Brusic:
> 
> > First of all: 0.90.2 is released? No announcement, but it's on the  
> > download page. Issues were still being tagged 0.90.2 several hours ago.
> > 
> > There is no separate client library. Jorg was working on one, but I do  
> > not know the status:  
> > [GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client](https://github.com/jprante/elasticsearch-client)  
> > [GitHub - jprante/elasticsearch-helper: Helper classes for Elasticsearch client](https://github.com/jprante/elasticsearch-support)
> > 
> > --  
> > Ivan
> > 
> > On Wed, Jun 26, 2013 at 5:32 AM, amos.wood \<[amos...@lifeway.com](mailto:amos...@lifeway.com)\<javascript:\>  
> > \<[mailto:amos...@lifeway.com](mailto:amos...@lifeway.com) \<javascript:\>\>\> wrote:
> > 
> > ```
> > We have a need for many of our services to build ElasticSearch 
> > JSON search requests and pass them into a separate service's REST 
> > endpoint that is actually doing the searches. In order to build 
> > the searches, they are utilizing the QueryBuilder, FilterBuilder, 
> > and SearchRequestBuilder classes from the 
> > "org.elasticsearch.search" package. Currently, we have to include 
> > the whole, heavy-weight "elasticsearch-0.90.2.jar" and dependent 
> > libraries into quite a few services to make this work which is 
> > causing issues with a large number of loaded classes and such in 
> > our service servers. It would be desirable to have some of the 
> > packages in the "elasticsearch-*.jar" files split into separate 
> > JAR files so that only the needed packages could be bundled into 
> > our WARs. 
> > 
> > Does anyone know if this has been done already by a third-party? 
> > 
> > Does anyone else have the same or similar needs so that this could 
> > be put on the to-be-developed list for ES? 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "elasticsearch" group. 
> > To unsubscribe from this group and stop receiving emails from it, 
> > send an email to elasticsearc...@googlegroups.com <javascript:> 
> > <mailto:elasticsearch%2Bunsubscribe@googlegroups.com <javascript:>>. 
> > 
> > ```
> 
> > ```
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > ```
> > 
> > --  
> > You received this message because you are subscribed to the Google  
> > Groups "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send  
> > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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:** [June 27, 2013, 12:44pm UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552/5 "2013-06-27T12:44:59Z")

</div>

OK, I will start over with a "client only" version based on 0.90.2 and  
come back to the list if I have any results.

Jörg

Am 27.06.13 14:42, schrieb amos.wood:

> We definitely have a need for a "client only" library.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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, 2:29am UTC](https://discuss.elastic.co/t/separate-es-library-for-search-request/12552/6 "2017-07-06T02:29:15Z")

</div>


