Elasticsearch+Hadoop read and write about elasticsearch-hadoop

[tzolov]

@marcelopaesrech this looks the same issue as #26. IMO there is no technical reason prohibiting this case.

Furthermore i've implemented a simple fix that adds ES_QUERY in addition to the ES_RESOURCE and it works fine.

[marcelopaesrech]

Yes, I want the input of Map is /radio/artists/_search?q=me* and the Reducers write to /radio/statistics (or maybe another index). Any intermediate data that Hadoop generates might be stored by hdfs, I don't care. But the final result I want to store in a index on ES.

I read your issue and is the same thing I think.

[costin]

@tzolov @marcelopaesrech hey, finally got around fixing this. Cascading/Hive and Pig set the read/write automatically - in case of MapReduce jobs one can use the es.resource.read and es.resource.write properties. es.resource is still supported and used as fall-back if the aforementioned properties are not defined.