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 am using 1.0.0. and see:
{
"error" : "SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[kwtJyjumSJ-DRx68nXaVhw][data][1]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][0]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][4]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][3]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][2]: ArrayIndexOutOfBoundsException[0]}]",
"status" : 500
}
when running date_histogram query. It happens when I run the query on the whole index while index is empty, or when I run the query on some type which has no documents (while other types in the index have docs).
Hi @bsmid,
This is indeed a bug, but the cause is different than what you describe (also based on your recreation above). It's caused when running a histogram or date_histogram on unmapped fields and then adding a sub-aggregation to them.
In the example above, even though you created a default mapping, you didn't actually index anything and no concrete mappings were created on the index.
In any case... I'll fix it soon...
Thx for reporting!
ps, you can remove the "index" : "not_analyzed" from the timestamp field... this setting only applies to string types
…date_/histogram aggregation was defined on unmapped field and also had a sub aggregation. The root cause there was that in such case, the estimated bucket count was 0, and the code was not designed to handle that well.
Closes#5179
…date_/histogram aggregation was defined on unmapped field and also had a sub aggregation. The root cause there was that in such case, the estimated bucket count was 0, and the code was not designed to handle that well.
Closes#5179
…date_/histogram aggregation was defined on unmapped field and also had a sub aggregation. The root cause there was that in such case, the estimated bucket count was 0, and the code was not designed to handle that well.
Closeselastic#5179
Hi,
I am using 1.0.0. and see:
{
"error" : "SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[kwtJyjumSJ-DRx68nXaVhw][data][1]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][0]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][4]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][3]: ArrayIndexOutOfBoundsException[0]}{[kwtJyjumSJ-DRx68nXaVhw][data][2]: ArrayIndexOutOfBoundsException[0]}]",
"status" : 500
}
when running date_histogram query. It happens when I run the query on the whole index while index is empty, or when I run the query on some type which has no documents (while other types in the index have docs).
Steps to reproduce:
The text was updated successfully, but these errors were encountered: