You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried PUTting {"index":{"auto_expand_replicas":"all"}} to an index and it came back with {"acknowledged":true}. However, in the logs there was a confusing explosion:
[2014-04-09 17:55:54,873][WARN ][cluster.metadata ] [hostname] failed to set [index.auto_expand_replicas], wrong format [all]
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
which was I did not find to be a helpful error message.
I thought that all was a legitimate value for this setting, and only through reading the source code did I learn that it is always range, even when providing all as the upper bound.
I have a fix for this usability problem, but the guidelines said I should discuss it first, so let's discuss.
The text was updated successfully, but these errors were encountered:
Previously if the user provided a non-conforming string, it would blow up with
`java.lang.StringIndexOutOfBoundsException: String index out of range: -1`
which is not a *helpful* error message.
Also updated the documentation to make the possible setting values more clear.
Close#5752
jpountz
changed the title
auto_expand_replicas explodes with a value of "all"
Settings: auto_expand_replicas explodes with a value of "all"
Jun 6, 2014
clintongormley
changed the title
Settings: auto_expand_replicas explodes with a value of "all"
Settings: Throw error when incorrect setting applied to auto_expand_replicas
Jul 16, 2014
clintongormley
changed the title
Settings: Throw error when incorrect setting applied to auto_expand_replicas
Throw error when incorrect setting applied to auto_expand_replicasJun 7, 2015
I tried PUTting
{"index":{"auto_expand_replicas":"all"}}
to an index and it came back with{"acknowledged":true}
. However, in the logs there was a confusing explosion:which was I did not find to be a helpful error message.
I thought that
all
was a legitimate value for this setting, and only through reading the source code did I learn that it is always range, even when providingall
as the upper bound.I have a fix for this usability problem, but the guidelines said I should discuss it first, so let's discuss.
The text was updated successfully, but these errors were encountered: