# Possible bug in RiversRouter.java (failed to get/parse \_meta) **URL:** \ **Category:** Elasticsearch\ **Created:** [July 12, 2011, 11:10am UTC](https://discuss.elastic.co/t/possible-bug-in-riversrouter-java-failed-to-get-parse--meta/4837 "2011-07-12T11:10:34Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![aleski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aleski/32/3171_2.png) [@aleski](https://discuss.elastic.co/u/aleski)\ **Post date:** [July 12, 2011, 11:10am UTC](https://discuss.elastic.co/t/possible-bug-in-riversrouter-java-failed-to-get-parse--meta/4837/1 "2011-07-12T11:10:34Z")
Hi, all! I've written a custom river running on ES 0.16.3 that reads from Amazon SQS. All worked well until I put the file "default- mapping.json" under config/. The file only sets "\_source": { "enabled: false } and that's all. Then I create my river using this request: curl -XPUT 'localhost:9200/\_river/myindex/\_meta' -d '{"type" : "amazonsqs"}' and I get: "...failed to get/parse \_meta for [myindex] java.lang.NullPointerException at org.elasticsearch.river.routing.RiversRouter $1.execute(RiversRouter.java:106)...." This is never thrown when config/default-mapping.json is deleted and the river recreated. I've tested this with 2 node cluster I got the same error. My shard/replica settings are 10/1. This issue might be a duplicate of the closed [https://github.com/elasticsearch/elasticsearch/issues/711](https://github.com/elasticsearch/elasticsearch/issues/711). Any solutions/workarounds would be appreciated. Thanks! ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 12, 2011, 5:07pm UTC](https://discuss.elastic.co/t/possible-bug-in-riversrouter-java-failed-to-get-parse--meta/4837/2 "2011-07-12T17:07:48Z")
Rivers definitions are stored as documents in the index, and when you disable source across the board using the default-mapping option, you also disable the source for those documents... . It shouldn't be this case, btw, can you open an issue? For now, you can disable source explicitly per index, or, using index templates to disable source. -shay.banon On Tuesday, July 12, 2011 at 2:10 PM, aleski wrote: > Hi, all! > > I've written a custom river running on ES 0.16.3 that reads from > Amazon SQS. All worked well until I put the file "default- > mapping.json" under config/. The file only sets "\_source": { "enabled: > false } and that's all. Then I create my river using this request: > > curl -XPUT 'localhost:9200/\_river/myindex/\_meta' -d '{"type" : > "amazonsqs"}' > > and I get: > > "...failed to get/parse \_meta for [myindex] > java.lang.NullPointerException > at org.elasticsearch.river.routing.RiversRouter > $1.execute(RiversRouter.java:106)...." > > This is never thrown when config/default-mapping.json is deleted and > the river recreated. I've tested this with 2 node cluster I got the > same error. My shard/replica settings are 10/1. > > This issue might be a duplicate of the closed > [River not recovered when using single node after shutdown · Issue #711 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/711). > > Any solutions/workarounds would be appreciated. Thanks! ---
**Author:** ![aleski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aleski/32/3171_2.png) [@aleski](https://discuss.elastic.co/u/aleski)\ **Post date:** [July 12, 2011, 10:55pm UTC](https://discuss.elastic.co/t/possible-bug-in-riversrouter-java-failed-to-get-parse--meta/4837/3 "2011-07-12T22:55:06Z")
Thanks, Shay! Issue opened here: [Overriding default mapping breaks river plugins · Issue #1117 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1117) On Jul 12, 8:07 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > Rivers definitions are stored as documents in the index, and when you disable source across the board using the default-mapping option, you also disable the source for those documents... . It shouldn't be this case, btw, can you open an issue? > > For now, you can disable source explicitly per index, or, using index templates to disable source. > > -shay.banon > > On Tuesday, July 12, 2011 at 2:10 PM, aleski wrote: > > > Hi, all! > > > I've written a custom river running on ES 0.16.3 that reads from > > Amazon SQS. All worked well until I put the file "default- > > mapping.json" under config/. The file only sets "\_source": { "enabled: > > false } and that's all. Then I create my river using this request: > > > curl -XPUT 'localhost:9200/\_river/myindex/\_meta' -d '{"type" : > > "amazonsqs"}' > > > and I get: > > > "...failed to get/parse \_meta for [myindex] > > java.lang.NullPointerException > > at org.elasticsearch.river.routing.RiversRouter > > $1.execute(RiversRouter.java:106)...." > > > This is never thrown when config/default-mapping.json is deleted and > > the river recreated. I've tested this with 2 node cluster I got the > > same error. My shard/replica settings are 10/1. > > > This issue might be a duplicate of the closed > > [River not recovered when using single node after shutdown · Issue #711 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/711). > > > Any solutions/workarounds would be appreciated. Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:00am UTC](https://discuss.elastic.co/t/possible-bug-in-riversrouter-java-failed-to-get-parse--meta/4837/4 "2017-07-06T04:00:55Z")
Closed on July 6, 2017, 4:00am UTC