# Decouple dependency of Java Client API on Lucene?

**URL:** <https://discuss.elastic.co/t/decouple-dependency-of-java-client-api-on-lucene/3126>\
**Category:** Elasticsearch\
**Created:** [July 20, 2010, 6:46pm UTC](https://discuss.elastic.co/t/decouple-dependency-of-java-client-api-on-lucene/3126 "2010-07-20T18:46:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Jensen\_2](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@David\_Jensen\_2](https://discuss.elastic.co/u/David_Jensen_2)\
**Post date:** [July 20, 2010, 6:46pm UTC](https://discuss.elastic.co/t/decouple-dependency-of-java-client-api-on-lucene/3126/1 "2010-07-20T18:46:22Z")

</div>

Would it be possible to decouple the dependency of the Java API on the  
Lucence jars? The result being a complete standalone Java API jar?

I could see where this might not be possible but it's worth a try to  
ask.

The reason why I need it is that we're currently running an older  
version of Lucene and while we migrate I would like to use the Java  
API to load the data (assuming the stuck TransportClient gets  
resolved) while we continue to run our current, old Lucene, search  
index. The alternative is to use the REST API, which were using now  
for testing, but according to Shay, the Java API should be faster.

David

---

<div class="post-metadata">

**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:** [July 20, 2010, 6:48pm UTC](https://discuss.elastic.co/t/decouple-dependency-of-java-client-api-on-lucene/3126/2 "2010-07-20T18:48:06Z")

</div>

In general, the TransportClient should not require the Lucene jars in order  
to work (the Node client does). Currently, I can't really validate it "on  
compile time" in the project, but if you hit a snag, then its not  
intentional and I will fix it.

-shay.banon

On Tue, Jul 20, 2010 at 9:46 PM, David Jensen [djensen47@gmail.com](mailto:djensen47@gmail.com) wrote:

> Would it be possible to decouple the dependency of the Java API on the  
> Lucence jars? The result being a complete standalone Java API jar?
> 
> I could see where this might not be possible but it's worth a try to  
> ask.
> 
> The reason why I need it is that we're currently running an older  
> version of Lucene and while we migrate I would like to use the Java  
> API to load the data (assuming the stuck TransportClient gets  
> resolved) while we continue to run our current, old Lucene, search  
> index. The alternative is to use the REST API, which were using now  
> for testing, but according to Shay, the Java API should be faster.
> 
> David

---

<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, 4:22am UTC](https://discuss.elastic.co/t/decouple-dependency-of-java-client-api-on-lucene/3126/3 "2017-07-06T04:22:00Z")

</div>

Closed on July 6, 2017, 4:22am UTC