# Supress routing

**URL:** <https://discuss.elastic.co/t/supress-routing/44778>\
**Category:** Elasticsearch\
**Created:** [March 17, 2016, 11:31pm UTC](https://discuss.elastic.co/t/supress-routing/44778 "2016-03-17T23:31:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ted.fed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ted.fed/32/56636_2.png) [@ted.fed](https://discuss.elastic.co/u/ted.fed)\
**Post date:** [March 17, 2016, 11:31pm UTC](https://discuss.elastic.co/t/supress-routing/44778/1 "2016-03-17T23:31:04Z")

</div>

We plan to use elasticsearch-hadoop bolt in storm with 2.x version of Elastic-Search.  
So we cannot use the es.mapping.routing option because that does not work with 2.x version.

And since we never want to search by ID, we just want that whatever ES-node gets the big bulk of documents, that node should consume those documents without distributing it any further (except its replicas).

Is there a way that I can disable routing in elastic-search via some configuration or custom-jar/plugin?

The code around [https://github.com/elastic/elasticsearch/blob/0aba19f4fa5c4fa2ac76ee96996d463a838248ac/core/src/main/java/org/elasticsearch/cluster/routing/OperationRouting.java#L175](https://github.com/elastic/elasticsearch/blob/0aba19f4fa5c4fa2ac76ee96996d463a838248ac/core/src/main/java/org/elasticsearch/cluster/routing/OperationRouting.java#L175) looks somewhat promising.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:07pm UTC](https://discuss.elastic.co/t/supress-routing/44778/2 "2017-07-05T23:07:22Z")

</div>


