Is the transport Java API open source too?

(Jonathan Aaron) #1

I'm trying to find the source for the transport client I use in my java app. Where is it located in github?


Looks like when I'm pulling in TransportClient from maven I'm really pulling down, Elasticsearch.jar from the client project, PrebultTransportClient from the client project, transport-netty3-client and transport-netty4-client from the modules project, lang-mustache-client and percolator-client. If I wanted to modify the TransportClient I would have to build out the elasticserach-core project to pull it into my project.

(David Pilato) #2


And you can start here:

(Jonathan Aaron) #3

Ah, that's great. I just built it. Thank you!

(Nik Everett) #4

The trouble with the transport client is that it is the same code as the elasticsearch server. This means that it makes decisions that aren't really right for a library. For instance, it uses log4j2. Not slf4j or some other logigng abstraction. It uses log4j2 directly. Anyway, that is why we're so keen to make a useable java client. Or, at least, we've been keen on it in the past few months.

(Jonathan Aaron) #5

I see. That explains why I had to add log4j to my test project. Thanks!

(Jonathan Aaron) #6

Is this the same TransportClient that I have in my Java Project. It looks like it's just the pre-built Transport client.

(Jonathan Aaron) #7

So If I modified the TransportClient in elasticsearch/core, how would I build it use in my Java Project? Does any of these projects build out a jar that I get from maven repo? ie:


(Jörg Prante) #8

The answer depends on your modification. What did you modify and why? Just out of curiosity.

(system) #9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.