# Just Pushed: More routing goodness

**URL:** <https://discuss.elastic.co/t/just-pushed-more-routing-goodness/3580>\
**Category:** Elasticsearch\
**Created:** [November 17, 2010, 3:54pm UTC](https://discuss.elastic.co/t/just-pushed-more-routing-goodness/3580 "2010-11-17T15:54:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**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:** [November 17, 2010, 3:54pm UTC](https://discuss.elastic.co/t/just-pushed-more-routing-goodness/3580/1 "2010-11-17T15:54:31Z")

</div>

Hi,

```
I added (the last) feature that I wanted to get into 0.13 release, and

```

it extends the routing support added (  
[https://github.com/elasticsearch/elasticsearch/issues/closed#issue/470](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/470)). The  
following are the features added:

1. Routing info is now stored automatically when indexing, and can be  
retrieved (in search/get) by specifying \_routing in the fields section. This  
helps when wanting to reindex the data. Here is the issue:  
[https://github.com/elasticsearch/elasticsearch/issues/closed#issue/515](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/515).
2. Routing can be defined in the mapping as required, and indexing  
operations will fail if one is not provided. This is added as an extra safe  
mechanism to make sure a data is not indexed with specific routing. Issue:  
[https://github.com/elasticsearch/elasticsearch/issues/closed#issue/520](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/520).
3. When \_routing is declared as required, a delete without explicit routing  
value gets broadcasted to the shards instead of hitting one (replication  
group). Issue:  
[https://github.com/elasticsearch/elasticsearch/issues/closed#issue/522](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/522).
4. A path can now be defined and the routing value can be automatically be  
extracted from an indexed document. Issue:  
[https://github.com/elasticsearch/elasticsearch/issues/closed#issue/524](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/524).

-shay.banon

---

<div class="post-metadata">

**Author:** ![medcl\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/medcl_2/32/3297_2.png) [@medcl\_2](https://discuss.elastic.co/u/medcl_2)\
**Post date:** [November 19, 2010, 4:55am UTC](https://discuss.elastic.co/t/just-pushed-more-routing-goodness/3580/2 "2010-11-19T04:55:43Z")

</div>

nice feature！！

On 11月17日, 下午11时54分, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:

> Hi,
> 
> ```
> I added (the last) feature that I wanted to get into 0.13 release, and
> 
> ```
> 
> it extends the routing support added ([Issues · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/470)). The  
> following are the features added:
> 
> 1. Routing info is now stored automatically when indexing, and can be  
> retrieved (in search/get) by specifying \_routing in the fields section. This  
> helps when wanting to reindex the data. Here is the issue:[Issues · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/515).
> 2. Routing can be defined in the mapping as required, and indexing  
> operations will fail if one is not provided. This is added as an extra safe  
> mechanism to make sure a data is not indexed with specific routing. Issue:[Issues · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/520).
> 3. When \_routing is declared as required, a delete without explicit routing  
> value gets broadcasted to the shards instead of hitting one (replication  
> group). Issue:[Issues · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/522).
> 4. A path can now be defined and the routing value can be automatically be  
> extracted from an indexed document. Issue:[Issues · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/closed#issue/524).
> 
> -shay.banon

---

<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 6, 2017, 4:16am UTC](https://discuss.elastic.co/t/just-pushed-more-routing-goodness/3580/3 "2017-07-06T04:16:17Z")

</div>