Thanks Sona,
This stack trace indicates a bug in the cardinality aggregation. I just
opened an issue for it:
https://github.com/elasticsearch/elasticsearch/issues/7429
In order to help me understand/reproduce this bug, could you please provide
the mappings of your ExamRowKey and body_part
Thanks Adrien.
The ExamRowKey and body_part are Strings uploaded from csv file using
LogStash to ElasticSearch.
- how reproducible is it? Ie. if you run this query 10 times, how many of
these queries will write such lines to the logs?
This query returns the error each time its run in the
One more update on the issue:
I tried changing the query using 'sum'
{
size:0,
aggs: {
group_by_BodyPart: {
terms: {
field: body_part,
size: 5,
order : { examcount : desc }
},
aggs : {
examcount : { sum : { field : ExamRowKey } }
Hi Adrien,
My elasticsearch version is : elasticsearch-1.2.1
The Maven dependency for hadoop:
dependency
groupIdorg.elasticsearch/groupId
artifactIdelasticsearch-hadoop-mr/artifactId
version2.0.1/version
/dependency
The full stack trace is given below:
[2014-08-25
Hi,
I was trying to run the below query from hadoop mapreduce:
{
aggs: {
group_by_body_part: {
terms: {
field: body_part,
size: 5,
order : { examcount : desc }
},
aggs: {
examcount: {
cardinality: {
field: ExamRowKey
Hi Sona,
Would you have the rest of the stack trace, I would like to know where the
ArrayIndexOutOfBoundsException occurred? What version of Elasticsearch are
you using?
On Fri, Aug 22, 2014 at 1:37 PM, Sona Samad sona.sa...@gmail.com wrote:
Hi,
I was trying to run the below query from
