# Read elasticsearch with Cascading

**URL:** <https://discuss.elastic.co/t/read-elasticsearch-with-cascading/63375>\
**Category:** Elasticsearch\
**Tags:** es-hadoop\
**Created:** [October 19, 2016, 10:47am UTC](https://discuss.elastic.co/t/read-elasticsearch-with-cascading/63375 "2016-10-19T10:47:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\
**Post date:** [October 27, 2016, 9:49pm UTC](https://discuss.elastic.co/t/read-elasticsearch-with-cascading/63375/2 "2016-10-27T21:49:11Z")

</div>

This looks like a similar issue to the [one you posted about Pig](https://discuss.elastic.co/t/export-elasticsearch-to-a-json-file-with-pig/63099/3). After taking a quick look at the code, I think it's also definitely a bug. I've opened an issue [here](https://github.com/elastic/elasticsearch-hadoop/issues/885).

With this showing up twice now, I'm also planning on doing a comprehensive review of the `es.output.json` feature. It seems to be a feature that is lacking in it's tests.

---

_[View the full topic](https://discuss.elastic.co/t/read-elasticsearch-with-cascading/63375)._