Java API or REST API for client development?

I believe this is true again. Aggregations API recently changed, and code
no longer compiles. The REST apis definitely change at a slower rate.

On Wednesday, March 26, 2014 8:12:56 AM UTC-4, Graham Tackley wrote:

Not true anymore: the java client has been compatible between minor
versions since 0.90 as far as I remember. 1.0.0 client is currently working
just fine against my 1.0.1 cluster, and my experimentation today shows that
it also works fine against 1.1.0. So this used to be a nightmare requiring
synchronised upgrades, but hasn't been for a while.

FWIW we use the java client (in transport client mode) extensively from
our scala apps, and it works brilliantly. I'd definitely recommend.

On Wednesday, 26 March 2014 11:45:19 UTC, Martin Forssen wrote:

The Java API is said to have better performance (and I believe that). The
drawbacks are that you must use the exact same version of the java API
library on the client as the server runs, as well as the same version of
Java. So upgrades suck.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/56137938-e3d8-456a-99b3-42465dcb6068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.