# Index Aliases: routing with \_update

**URL:** <https://discuss.elastic.co/t/index-aliases-routing-with--update/8689>\
**Category:** Elasticsearch\
**Created:** [August 9, 2012, 5:31am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689 "2012-08-09T05:31:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\
**Post date:** [August 9, 2012, 5:31am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/1 "2012-08-09T05:31:46Z")

</div>

Hi,

As I can see, when I use index aliases with specified routing, everything  
works fine (indexing and searching), but \_update does not follow the  
routing setting from the alias. Is that ok or there is something wrong at  
my end ? If this is not right behavior I will give an example here.

Best regards.  
Marcin Dojwa.

---

<div class="post-metadata">

**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\
**Post date:** [August 9, 2012, 5:36am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/2 "2012-08-09T05:36:29Z")

</div>

OK, I am sure that \_update does not follow the routing value from alias  
because adding 'routing' value to the \_update query fixed the problem.

Best regards.

2012/8/9 Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com)

> Hi,
> 
> As I can see, when I use index aliases with specified routing, everything  
> works fine (indexing and searching), but \_update does not follow the  
> routing setting from the alias. Is that ok or there is something wrong at  
> my end ? If this is not right behavior I will give an example here.
> 
> Best regards.  
> Marcin Dojwa.

---

<div class="post-metadata">

**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\
**Post date:** [August 9, 2012, 5:44am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/3 "2012-08-09T05:44:08Z")

</div>

## I forgot to ask if this will be fixed and possibly when ? 🙂 Unfortunately this does not allow to do what is told in [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/videos/2012/06/05/big-data-search-and-analytics.html)

I mean the part about extracting huge users to separated indexes in "Users"  
data flow section. Hardcoding routing parameter for every \_update in  
applications makes it imposible split extracted huge user to separated  
index into more than one shard.

Thanks for help.

Best regards.

2012/8/9 Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com)

> OK, I am sure that \_update does not follow the routing value from alias  
> because adding 'routing' value to the \_update query fixed the problem.
> 
> Best regards.
> 
> 2012/8/9 Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com)
> 
> > Hi,
> > 
> > As I can see, when I use index aliases with specified routing, everything  
> > works fine (indexing and searching), but \_update does not follow the  
> > routing setting from the alias. Is that ok or there is something wrong at  
> > my end ? If this is not right behavior I will give an example here.
> > 
> > Best regards.  
> > Marcin Dojwa.

---

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [August 9, 2012, 11:36am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/4 "2012-08-09T11:36:34Z")

</div>

On Thu, 2012-08-09 at 07:44 +0200, Marcin Dojwa wrote:

> I forgot to ask if this will be fixed and possibly when ? 🙂

I suggest opening an issue with a curl replication of the problem -  
quickest way to get somebody working on it

clint

---

<div class="post-metadata">

**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\
**Post date:** [August 9, 2012, 11:40am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/5 "2012-08-09T11:40:05Z")

</div>

Thanks, I asked here because I was no sure if this is a bug or it just  
works like this 🙂 I will open the ticket as you said.

Best regards.

2012/8/9 Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)

> On Thu, 2012-08-09 at 07:44 +0200, Marcin Dojwa wrote:
> 
> > I forgot to ask if this will be fixed and possibly when ? 🙂
> 
> I suggest opening an issue with a curl replication of the problem -  
> quickest way to get somebody working on it
> 
> clint

---

<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:** [August 9, 2012, 1:07pm UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/6 "2012-08-09T13:07:58Z")

</div>

Heya, its a bug, I have already recreated it with a test case, will open an issue and it will be fixed in the next 0.19 release. Here is the issue: [Update API: Update through an alias with routing configured on it fail to use the routing · Issue #2155 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2155).

On Aug 9, 2012, at 1:40 PM, Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com) wrote:

> Thanks, I asked here because I was no sure if this is a bug or it just works like this 🙂 I will open the ticket as you said.
> 
> Best regards.
> 
> 2012/8/9 Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)  
> On Thu, 2012-08-09 at 07:44 +0200, Marcin Dojwa wrote:
> 
> > I forgot to ask if this will be fixed and possibly when ? 🙂
> 
> I suggest opening an issue with a curl replication of the problem -  
> quickest way to get somebody working on it
> 
> clint

---

<div class="post-metadata">

**Author:** ![Marcin\_Dojwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcin_dojwa/32/2307_2.png) [@Marcin\_Dojwa](https://discuss.elastic.co/u/Marcin_Dojwa)\
**Post date:** [August 9, 2012, 1:26pm UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/7 "2012-08-09T13:26:59Z")

</div>

Thank you very much for this, it would be huge fix for me 🙂

Best regards.

2012/8/9 Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com)

> Heya, its a bug, I have already recreated it with a test case, will open  
> an issue and it will be fixed in the next 0.19 release. Here is the issue:  
> [Update API: Update through an alias with routing configured on it fail to use the routing · Issue #2155 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2155).
> 
> On Aug 9, 2012, at 1:40 PM, Marcin Dojwa [m.dojwa@livechatinc.com](mailto:m.dojwa@livechatinc.com) wrote:
> 
> Thanks, I asked here because I was no sure if this is a bug or it just  
> works like this 🙂 I will open the ticket as you said.
> 
> Best regards.
> 
> 2012/8/9 Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)
> 
> > On Thu, 2012-08-09 at 07:44 +0200, Marcin Dojwa wrote:
> > 
> > > I forgot to ask if this will be fixed and possibly when ? 🙂
> > 
> > I suggest opening an issue with a curl replication of the problem -  
> > quickest way to get somebody working on it
> > 
> > clint

---

<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, 3:16am UTC](https://discuss.elastic.co/t/index-aliases-routing-with--update/8689/8 "2017-07-06T03:16:57Z")

</div>


