Logically, I understand that the curl statement cannot be faster. Which is
how I reckon that I'm doing something wrong. This is how I am timing my
methods (from my own dev machine pointing to a vm) using the Google
stopwatch and ticker.
*Client connection to myvm:9300 using java:*
I have written a test case, in the hope it is useful ... (it's for
1.0.0.RC1)
https://gist.github.com/jprante/8568886
Jörg
--
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
Replace new IndicesGetAliasesRequest() with new
GetAliasesRequest(null), this should work
See also RestGetAliasesAction.java
Jörg
--
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,
The easiest way to find out how to use the Java API equivalent of a REST
call is to simply look up the RestAction class. In this case:
Thanks,
Jôrg's tip didn't work. Null was not accepted in the constructor. We
might be using a different version of ElasticSearch.
However, I did find the 0.90.10 equivalent of the class Ivan suggested.
I'm guessing that's as close as I can get to reproducing the _alias
request. I tried to
Yes, asking the cluster state is possible to filter out for aliases (that
is what the TransportGetAliasesAction is doing, too)
I was using 1.0.0.RC1, RestGetIndicesAliasAction is deprecated in 1.0.0.RC1
A null argument to GetAliasesRequest gives an NPE, but an empty string
works: