Thift Java API and Maven


(Ed Brown VSTI) #1

Hello.
I'm experimenting with ElasticSearch and want to experiment with the
Java API and the Thift connection.

I've installed the Thrift plugin and when I start ElasticSearch, I see
that it starts the Thrift transport. When I included the Thrift
dependency in the Maven POM, Maven complains with: "Missing artifact
org.elasticsearch:es-libthrift:jar:0.6.1:compile"

The Maven dependency used follows:

org.elasticsearch elasticsearch-transport-thrift 0.17.1 jar

Your help is appreciated.
Thanks.


(Shay Banon) #2

What are you trying to do? If oyu want to connect to elasticsearch using hte
Java API, you don't need thrift, you can connect using the "native"
connection by constructing a client. If you want to use thrift, you need to
build your own thrift bindings and use thrift lib yourself. Note, the thrift
API is a simple wrapper around the REST API, its similar in nature to
connecting using HTTP.

On Wed, Aug 10, 2011 at 4:41 PM, Ed Brown VSTI edbrownvsti@gmail.comwrote:

Hello.
I'm experimenting with ElasticSearch and want to experiment with the
Java API and the Thift connection.

I've installed the Thrift plugin and when I start ElasticSearch, I see
that it starts the Thrift transport. When I included the Thrift
dependency in the Maven POM, Maven complains with: "Missing artifact
org.elasticsearch:es-libthrift:jar:0.6.1:compile"

The Maven dependency used follows:

org.elasticsearch elasticsearch-transport-thrift 0.17.1 jar

Your help is appreciated.
Thanks.


(Ed Brown VSTI) #3

I'm trying to determine the most performant method of doing indexing
and thought I understood using the Thrift transport was faster.

On Aug 10, 10:03 am, Shay Banon kim...@gmail.com wrote:

What are you trying to do? If oyu want to connect to elasticsearch using hte
Java API, you don't need thrift, you can connect using the "native"
connection by constructing a client. If you want to use thrift, you need to
build your own thrift bindings and use thrift lib yourself. Note, the thrift
API is a simple wrapper around the REST API, its similar in nature to
connecting using HTTP.

On Wed, Aug 10, 2011 at 4:41 PM, Ed Brown VSTI edbrownv...@gmail.comwrote:

Hello.
I'm experimenting with ElasticSearch and want to experiment with the
Java API and the Thift connection.

I've installed the Thrift plugin and when I start ElasticSearch, I see
that it starts the Thrift transport. When I included the Thrift
dependency in the Maven POM, Maven complains with: "Missing artifact
org.elasticsearch:es-libthrift:jar:0.6.1:compile"

The Maven dependency used follows:

org.elasticsearch elasticsearch-transport-thrift 0.17.1 jar

Your help is appreciated.
Thanks.- Hide quoted text -

  • Show quoted text -

(Shay Banon) #4

If you use Java, then the "pure" Java API is the fastest. HTTP as a
transport is actually not that slow, its just that some clients perform
badly with it.

On Wed, Aug 10, 2011 at 8:56 PM, Ed Brown VSTI edbrownvsti@gmail.comwrote:

I'm trying to determine the most performant method of doing indexing
and thought I understood using the Thrift transport was faster.

On Aug 10, 10:03 am, Shay Banon kim...@gmail.com wrote:

What are you trying to do? If oyu want to connect to elasticsearch using
hte
Java API, you don't need thrift, you can connect using the "native"
connection by constructing a client. If you want to use thrift, you need
to
build your own thrift bindings and use thrift lib yourself. Note, the
thrift
API is a simple wrapper around the REST API, its similar in nature to
connecting using HTTP.

On Wed, Aug 10, 2011 at 4:41 PM, Ed Brown VSTI <edbrownv...@gmail.com
wrote:

Hello.
I'm experimenting with ElasticSearch and want to experiment with the
Java API and the Thift connection.

I've installed the Thrift plugin and when I start ElasticSearch, I see
that it starts the Thrift transport. When I included the Thrift
dependency in the Maven POM, Maven complains with: "Missing artifact
org.elasticsearch:es-libthrift:jar:0.6.1:compile"

The Maven dependency used follows:

org.elasticsearch elasticsearch-transport-thrift 0.17.1 jar

Your help is appreciated.
Thanks.- Hide quoted text -

  • Show quoted text -

(Shay Banon) #5

One more thing, the Java API uses an internal communication transport, not
HTTP.

On Wed, Aug 10, 2011 at 9:16 PM, Shay Banon kimchy@gmail.com wrote:

If you use Java, then the "pure" Java API is the fastest. HTTP as a
transport is actually not that slow, its just that some clients perform
badly with it.

On Wed, Aug 10, 2011 at 8:56 PM, Ed Brown VSTI edbrownvsti@gmail.comwrote:

I'm trying to determine the most performant method of doing indexing
and thought I understood using the Thrift transport was faster.

On Aug 10, 10:03 am, Shay Banon kim...@gmail.com wrote:

What are you trying to do? If oyu want to connect to elasticsearch using
hte
Java API, you don't need thrift, you can connect using the "native"
connection by constructing a client. If you want to use thrift, you need
to
build your own thrift bindings and use thrift lib yourself. Note, the
thrift
API is a simple wrapper around the REST API, its similar in nature to
connecting using HTTP.

On Wed, Aug 10, 2011 at 4:41 PM, Ed Brown VSTI <edbrownv...@gmail.com
wrote:

Hello.
I'm experimenting with ElasticSearch and want to experiment with the
Java API and the Thift connection.

I've installed the Thrift plugin and when I start ElasticSearch, I see
that it starts the Thrift transport. When I included the Thrift
dependency in the Maven POM, Maven complains with: "Missing artifact
org.elasticsearch:es-libthrift:jar:0.6.1:compile"

The Maven dependency used follows:

org.elasticsearch elasticsearch-transport-thrift 0.17.1 jar

Your help is appreciated.
Thanks.- Hide quoted text -

  • Show quoted text -

(Ed Brown VSTI) #6

Thank you very much for your responses.

From what I can tell right now, this is a good product.

On Aug 10, 2:16 pm, Shay Banon kim...@gmail.com wrote:

One more thing, the Java API uses an internal communication transport, not
HTTP.

On Wed, Aug 10, 2011 at 9:16 PM, Shay Banon kim...@gmail.com wrote:

If you use Java, then the "pure" Java API is the fastest. HTTP as a
transport is actually not that slow, its just that some clients perform
badly with it.

On Wed, Aug 10, 2011 at 8:56 PM, Ed Brown VSTI edbrownv...@gmail.comwrote:

I'm trying to determine the most performant method of doing indexing
and thought I understood using the Thrift transport was faster.

On Aug 10, 10:03 am, Shay Banon kim...@gmail.com wrote:

What are you trying to do? If oyu want to connect to elasticsearch using
hte
Java API, you don't need thrift, you can connect using the "native"
connection by constructing a client. If you want to use thrift, you need
to
build your own thrift bindings and use thrift lib yourself. Note, the
thrift
API is a simple wrapper around the REST API, its similar in nature to
connecting using HTTP.

On Wed, Aug 10, 2011 at 4:41 PM, Ed Brown VSTI <edbrownv...@gmail.com
wrote:

Hello.
I'm experimenting with ElasticSearch and want to experiment with the
Java API and the Thift connection.

I've installed the Thrift plugin and when I start ElasticSearch, I see
that it starts the Thrift transport. When I included the Thrift
dependency in the Maven POM, Maven complains with: "Missing artifact
org.elasticsearch:es-libthrift:jar:0.6.1:compile"

The Maven dependency used follows:

org.elasticsearch elasticsearch-transport-thrift 0.17.1 jar

Your help is appreciated.
Thanks.- Hide quoted text -

  • Show quoted text -- Hide quoted text -
  • Show quoted text -

(system) #7