-Hadoop and Hadoop-ES
no problem with Hadoop2ES with these 3 settings ( i see the index + data
through head plugin, perfect)
job.set(es.resource, eshindex2/eshlog2);
job.set(es.host, localhost);
job.set(es.port, 9200);
but experimenting the inverse , ie ES 2 Hadoop
hello my context:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java
i am experimenting ES-Hadoop and Hadoop-ES
no problem with Hadoop2ES with these 3 settings ( i see the index + data
through head plugin, perfect)
job.set(es.resource, eshindex2/eshlog2);
job.set(es.host, localhost
should use es.resource instead of es.query in your
latest example.
es.query is supported in the upcoming 1.3.0.M2 (not in m1).
On 04/02/2014 12:01 PM, Phil gib wrote:
hello my context:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java
i am experimenting ES-Hadoop and Hadoop-ES
.M2 (not in m1).
On 04/02/2014 12:01 PM, Phil gib wrote:
hello my context:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java
i am experimenting ES-Hadoop and Hadoop-ES
no problem with Hadoop2ES with these 3 settings ( i see the index +
data through head
.
es.query is supported in the upcoming 1.3.0.M2 (not in m1).
On 04/02/2014 12:01 PM, Phil gib wrote:
hello my context:
ES 0.90.3, elasticsearch-hadoop-1.3.0.M1 , eclipse- java
i am experimenting ES-Hadoop and Hadoop-ES
no problem with Hadoop2ES with these 3