Index Aliases: routing with _update

Elastic Stack Elasticsearch
1

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.

2

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

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.

3

I forgot to ask if this will be fixed and possibly when ? :slight_smile: Unfortunately
this does not allow to do what is told in
Elasticsearch Platform — Find real-time answers at scale | Elastic

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

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

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.

4

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

I forgot to ask if this will be fixed and possibly when ? :slight_smile:

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

clint

5

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

Best regards.

2012/8/9 Clinton Gormley 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 ? :slight_smile:

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

clint

6

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.

On Aug 9, 2012, at 1:40 PM, Marcin Dojwa 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 :slight_smile: I will open the ticket as you said.

Best regards.

2012/8/9 Clinton Gormley 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 ? :slight_smile:

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

clint

7

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

Best regards.

2012/8/9 Shay Banon 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.

On Aug 9, 2012, at 1:40 PM, Marcin Dojwa 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 :slight_smile: I will open the ticket as you said.

Best regards.

2012/8/9 Clinton Gormley 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 ? :slight_smile:

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

clint