New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MultiPercolateRequest breaks when setting Routing #6214
Comments
@martijnvg could you look at this one please? |
martijnvg
added a commit
that referenced
this issue
Jan 7, 2015
…e request causing an ArrayIndexOutOfBoundsException. The multi percolate shard responses are collected in an atomic array which uses the shard id is used as index, but the number of shards the multi percolate request was meant to go to was used as size of this array instead the total number of shards an index has. This caused the exception when routing was used. Closes #6214
martijnvg
added a commit
that referenced
this issue
Jan 7, 2015
…e request causing an ArrayIndexOutOfBoundsException. The multi percolate shard responses are collected in an atomic array which uses the shard id is used as index, but the number of shards the multi percolate request was meant to go to was used as size of this array instead the total number of shards an index has. This caused the exception when routing was used. Closes #6214
martijnvg
added a commit
that referenced
this issue
Jan 7, 2015
…e request causing an ArrayIndexOutOfBoundsException. The multi percolate shard responses are collected in an atomic array which uses the shard id is used as index, but the number of shards the multi percolate request was meant to go to was used as size of this array instead the total number of shards an index has. This caused the exception when routing was used. Closes #6214
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…e request causing an ArrayIndexOutOfBoundsException. The multi percolate shard responses are collected in an atomic array which uses the shard id is used as index, but the number of shards the multi percolate request was meant to go to was used as size of this array instead the total number of shards an index has. This caused the exception when routing was used. Closes elastic#6214
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…e request causing an ArrayIndexOutOfBoundsException. The multi percolate shard responses are collected in an atomic array which uses the shard id is used as index, but the number of shards the multi percolate request was meant to go to was used as size of this array instead the total number of shards an index has. This caused the exception when routing was used. Closes elastic#6214
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Edit test:
https://github.com/elasticsearch/elasticsearch/blob/master/src/test/java/org/elasticsearch/percolator/MultiPercolatorTests.java
The text was updated successfully, but these errors were encountered: