Get aliases for specific aliases returns all indices

[jasontedor]

I think the behavior specified in IndexAliasesIT#testIndicesGetAliases is wrong. Namely:

• create indices foobar, test, test123, foobarbaz, bazbar
• add an alias alias1 -> foobar
• add an alias alias2 -> foobar
• execute get aliases on the transport layer specifying alias1 as the only alias to get
• the response includes foobar, test, test123, foobarbaz, bazbar albeit with empty alias metadata for all indices except foobar which contains alias1 only
• previously the response would only contain foobar with alias metadata for alias1

This was a breaking change resulting from #25114, the specific change in behavior arising from a change to MetaData.

I am opening this personally considering it a bug but for discussion where we might decide to only document this behavior (not my preference, I think this behavior is weird and not intuitive).

Relates #27743

[dakrone]

It's worth noting that this only affects the transport layer. The REST layer doesn't include the extra indices. The transport layer should probably be changed to return only indices that contain the alias when an alias name is specified.

[jasontedor]

The transport client is exactly what this issue is being reported for.

[antitech]

@jasontedor @dakrone
Yes Transport client got affected. Now we are explicitly filtering the indices which contains AliasMetaData. Its performance hit too for our application.

In which release /version we can expect its fix.?

[dakrone]

The transport client is exactly what this issue is being reported for.

Yes I understand, I was only clarifying for the sake of other people reading.

…

On Dec 12, 2017 9:51 PM, "Jason Tedor" ***@***.***> wrote: The transport client is exactly what this issue is being reported for. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#27763 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABKdIlsoCe_HDhcnutz3ym833dV9H3Nks5s_1fNgaJpZM4Q-Cu4> .

[jasontedor]

In which release /version we can expect its fix.?

Right now you can not have any expectation, no decision has been reached.

[s1monw]

+1

[jasontedor]

We discussed this in Fix-it-Friday and agree that this is a bug. Would you take care of this @dakrone.

[jasontedor]

@antitech I want to be clear that while we agree this is bug, it is not a high priority bug so there is no expectation about the timeline for a fix.

[antitech]

@jasontedor its ok. I'll apply any temporary fix for now . Just a request can you please attach this bug with aliases tag.