ElasticsearchIllegalArgumentException when _only_nodes is used as a search preference

[ppf2]

I can reproduce this using REST and Java API + ES 1.7.0

The following works:

GET /_search?explain&preference=_only_node:6qdURxYySpCWugwxuvIH3g

The following throws the error:

GET /_search?explain&preference=_only_nodes:pod:A

{"error":"ElasticsearchIllegalArgumentException[no Preference for [_only_nodes]]","status":400}

I am able to workaround this by using the ENUM value from org.elasticsearch.cluster.routing.operation.plain.Preference directly:

The following works:
GET /_search?explain&preference=ONLY_NODES:pod:A

_only_nodes should work just like _only_node (and not require using the ONLY_NODES enum)?

[nirmalc]

its broken in 1.7 as "_only_nodes" is not parsed to right preference. (
Preference.java - parse )

Thanks
Nirmal

On Tue, Jul 21, 2015 at 7:08 PM, Pius notifications@github.com wrote:

I can reproduce this using REST and Java API + ES 1.7.0

The following works:

GET /_search?explain&preference=_only_node:6qdURxYySpCWugwxuvIH3g

The following throws the error:

GET /_search?explain&preference=_only_nodes:pod:A

{"error":"ElasticsearchIllegalArgumentException[no Preference for [_only_nodes]]","status":400}

I am able to workaround this by using the ENUM value from
org.elasticsearch.cluster.routing.operation.plain.Preference directly:

The following works:
GET /_search?explain&preference=ONLY_NODES:pod:A

_only_nodes should work just like _only_node?

—
Reply to this email directly or view it on GitHub
#12389.

[clintongormley]

@nirmalc want to send a fix?

[nirmalc]

@clintongormley , will look at it today and send fix. I think its minor merge issue with 1.7 tree

[nirmalc]

@ppf2 - using enum directly doesnt actually work ; its considering preference as custom string value probably. we consider it as custom preference if preference value begins with "_"

[ppf2]

@nirmalc yah you are right, was testing with just 2 nodes, so it appeared that it worked with ONLY_NODES when switching the node attributes but in fact it was just treating them as custom routing values. Thx for submitting the fix 👍

[spinscale]

Closed by 2fa7404