# Is it possible to avoid / ignore ClassCastExceptions in aggregations?
**URL:** https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167
**Category:** Elasticsearch
**Created:** [December 9, 2014, 5:47pm UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167 "2014-12-09T17:47:34Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Nuno\_Lopes](https://discuss.elastic.co/u/Nuno_Lopes)
#### Post date: [December 9, 2014, 5:47pm UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167/1 "2014-12-09T17:47:34Z")
Hello all,
Consider the following mapping:
PUT /test/value/\_mapping
{
"properties": {
"value": {
"type": "string",
"index": "analyzed",
"index\_analyzer": "standard",
"search\_analyzer": "standard",
"fields": {
"integer": {
"type": "integer",
"ignore\_malformed": true
},
"double": {
"type": "double",
"ignore\_malformed": true
},
"date": {
"type": "date",
"ignore\_malformed": true }
}
}
}
}
with simply these documents:
PUT /test/value/1
{
"value": "v1"
}
PUT /test/value/2
{
"value": "2"
}
Writing this aggregation the whole response consists of a
ClassCastException:
POST /test/\_search
{
"aggregations": {
"a1": {
"terms": {
"field": "value"
}
},
"a2": {
"max": {
"field": "value"
}
}
}
}
When I'm writing this query I know this is the case but in my application
I'm generating different kinds of aggregations (from which some will give
ClassCastExceptions but I have no easy way of knowing which beforehand).
Is there a way to ignore an aggregation that is invalid and return the
results of the ones which are valid? And similarly, would this work for
nested aggregations?
## Thank you, best regards,
Nuno Lopes
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [December 9, 2014, 5:51pm UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167/2 "2014-12-09T17:51:51Z")
If you want to compute on numerical values, you need to use the right field name.
value is a String. So you can’t use it for max agg.
You could try with "value.integer". I think it should work.
--
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)
@dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> Le 9 déc. 2014 à 18:47, Nuno Lopes [nuno.alexandre.lopes@gmail.com](mailto:nuno.alexandre.lopes@gmail.com) a écrit :
>
> Hello all,
>
> Consider the following mapping:
>
> PUT /test/value/\_mapping
> {
> "properties": {
> "value": {
> "type": "string",
> "index": "analyzed",
> "index\_analyzer": "standard",
> "search\_analyzer": "standard",
> "fields": {
> "integer": {
> "type": "integer",
> "ignore\_malformed": true
> },
> "double": {
> "type": "double",
> "ignore\_malformed": true
> },
> "date": {
> "type": "date",
> "ignore\_malformed": true }
> }
> }
> }
> }
>
> with simply these documents:
>
> PUT /test/value/1
>
> {
> "value": "v1"
> }
> PUT /test/value/2
> {
> "value": "2"
> }
>
> Writing this aggregation the whole response consists of a ClassCastException:
>
> POST /test/\_search
> {
> "aggregations": {
> "a1": {
> "terms": {
> "field": "value"
> }
> },
> "a2": {
> "max": {
> "field": "value"
> }
> }
> }
> }
>
> When I'm writing this query I know this is the case but in my application I'm generating different kinds of aggregations (from which some will give ClassCastExceptions but I have no easy way of knowing which beforehand). Is there a way to ignore an aggregation that is invalid and return the results of the ones which are valid? And similarly, would this work for nested aggregations?
>
> ## Thank you, best regards,
>
> Nuno Lopes
>
> --
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com) [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com?utm_medium=email&utm_source=footer).
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout) [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9B83B8EC-C9B2-42C8-9505-4A489333BD05%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/9B83B8EC-C9B2-42C8-9505-4A489333BD05%40pilato.fr).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Nuno\_Lopes](https://discuss.elastic.co/u/Nuno_Lopes)
#### Post date: [December 9, 2014, 6:01pm UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167/3 "2014-12-09T18:01:19Z")
Hi David, Thanks for the reply.
Actually a more adequate example is below. What we're trying to do is
apply the same aggregation over the different types even though we already
know some aggregations will fail (only using string and integer for this
example). However, is there a way to ignore the ones that fail and have
the results for the valid aggregations? The behaviour I'm finding is that
as long as one aggregation is invalid, we just get the error back. And
would such solution also work over nested aggregations?
POST /test/\_search
{
"aggregations": {
"a1": {
"max": {
"field": "value"
}
},
"a2": {
"max": {
"field": "value.integer"
}
}
}
}
On Tuesday, December 9, 2014 5:53:19 PM UTC, David Pilato wrote:
> If you want to compute on numerical values, you need to use the right
> field name.
> value is a String. So you can’t use it for max agg.
>
> You could try with "value.integer". I think it should work.
>
> --
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)
> [http://Elasticsearch.com](http://Elasticsearch.com)_
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr
> [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs
> [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
>
> Le 9 déc. 2014 à 18:47, Nuno Lopes \<[nuno.alexa...@gmail.com](mailto:nuno.alexa...@gmail.com) \\>
> a écrit :
>
> Hello all,
>
> Consider the following mapping:
>
> PUT /test/value/\_mapping
> {
> "properties": {
> "value": {
> "type": "string",
> "index": "analyzed",
> "index\_analyzer": "standard",
> "search\_analyzer": "standard",
> "fields": {
> "integer": {
> "type": "integer",
> "ignore\_malformed": true
> },
> "double": {
> "type": "double",
> "ignore\_malformed": true
> },
> "date": {
> "type": "date",
> "ignore\_malformed": true }
> }
> }
> }
> }
>
> with simply these documents:
>
> PUT /test/value/1
>
> {
> "value": "v1"
> }
> PUT /test/value/2
> {
> "value": "2"
> }
>
> Writing this aggregation the whole response consists of a
> ClassCastException:
>
> POST /test/\_search
> {
> "aggregations": {
> "a1": {
> "terms": {
> "field": "value"
> }
> },
> "a2": {
> "max": {
> "field": "value"
> }
> }
> }
> }
>
> When I'm writing this query I know this is the case but in my application
> I'm generating different kinds of aggregations (from which some will give
> ClassCastExceptions but I have no easy way of knowing which beforehand).
> Is there a way to ignore an aggregation that is invalid and return the
> results of the ones which are valid? And similarly, would this work for
> nested aggregations?
>
> ## Thank you, best regards,
>
> Nuno Lopes
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \.
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com)
> [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com?utm_medium=email&utm_source=footer)
> .
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [December 9, 2014, 6:10pm UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167/4 "2014-12-09T18:10:32Z")
May be a filter agg using a exist filter could help?
--
David 😉
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> Le 9 déc. 2014 à 19:01, Nuno Lopes [nuno.alexandre.lopes@gmail.com](mailto:nuno.alexandre.lopes@gmail.com) a écrit :
>
> Hi David, Thanks for the reply.
>
> Actually a more adequate example is below. What we're trying to do is apply the same aggregation over the different types even though we already know some aggregations will fail (only using string and integer for this example). However, is there a way to ignore the ones that fail and have the results for the valid aggregations? The behaviour I'm finding is that as long as one aggregation is invalid, we just get the error back. And would such solution also work over nested aggregations?
>
> POST /test/\_search
> {
> "aggregations": {
> "a1": {
> "max": {
> "field": "value"
> }
> },
> "a2": {
> "max": {
> "field": "value.integer"
> }
> }
> }
> }
>
> > On Tuesday, December 9, 2014 5:53:19 PM UTC, David Pilato wrote:
> > If you want to compute on numerical values, you need to use the right field name.
> > value is a String. So you can’t use it for max agg.
> >
> > You could try with "value.integer". I think it should work.
> >
> > --
> > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)
> > @dadoonet | @elasticsearchfr | @scrutmydocs
> >
> > > Le 9 déc. 2014 à 18:47, Nuno Lopes [nuno.alexa...@gmail.com](mailto:nuno.alexa...@gmail.com) a écrit :
> > >
> > > Hello all,
> > >
> > > Consider the following mapping:
> > >
> > > PUT /test/value/\_mapping
> > > {
> > > "properties": {
> > > "value": {
> > > "type": "string",
> > > "index": "analyzed",
> > > "index\_analyzer": "standard",
> > > "search\_analyzer": "standard",
> > > "fields": {
> > > "integer": {
> > > "type": "integer",
> > > "ignore\_malformed": true
> > > },
> > > "double": {
> > > "type": "double",
> > > "ignore\_malformed": true
> > > },
> > > "date": {
> > > "type": "date",
> > > "ignore\_malformed": true }
> > > }
> > > }
> > > }
> > > }
> > >
> > > with simply these documents:
> > >
> > > PUT /test/value/1
> > >
> > > {
> > > "value": "v1"
> > > }
> > > PUT /test/value/2
> > > {
> > > "value": "2"
> > > }
> > >
> > > Writing this aggregation the whole response consists of a ClassCastException:
> > >
> > > POST /test/\_search
> > > {
> > > "aggregations": {
> > > "a1": {
> > > "terms": {
> > > "field": "value"
> > > }
> > > },
> > > "a2": {
> > > "max": {
> > > "field": "value"
> > > }
> > > }
> > > }
> > > }
> > >
> > > When I'm writing this query I know this is the case but in my application I'm generating different kinds of aggregations (from which some will give ClassCastExceptions but I have no easy way of knowing which beforehand). Is there a way to ignore an aggregation that is invalid and return the results of the ones which are valid? And similarly, would this work for nested aggregations?
> > >
> > > ## Thank you, best regards,
> > >
> > > Nuno Lopes
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com).
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
>
> --
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com).
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/A00603D0-C594-4790-A99E-33CD00F034E5%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/A00603D0-C594-4790-A99E-33CD00F034E5%40pilato.fr).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Nuno\_Lopes](https://discuss.elastic.co/u/Nuno_Lopes)
#### Post date: [December 9, 2014, 7:14pm UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167/5 "2014-12-09T19:14:29Z")
Good idea, that might work for the "inner" fields, however the "string" is
always present so we'll still get the error. I might play around with
changing the mapping to try to adopt your solution if all else fails..
On Tuesday, December 9, 2014 6:11:02 PM UTC, David Pilato wrote:
> May be a filter agg using a exist filter could help?
>
> --
> David 😉
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 9 déc. 2014 à 19:01, Nuno Lopes \<[nuno.alexa...@gmail.com](mailto:nuno.alexa...@gmail.com) \\>
> a écrit :
>
> Hi David, Thanks for the reply.
>
> Actually a more adequate example is below. What we're trying to do is
> apply the same aggregation over the different types even though we already
> know some aggregations will fail (only using string and integer for this
> example). However, is there a way to ignore the ones that fail and have
> the results for the valid aggregations? The behaviour I'm finding is that
> as long as one aggregation is invalid, we just get the error back. And
> would such solution also work over nested aggregations?
>
> POST /test/\_search
> {
> "aggregations": {
> "a1": {
> "max": {
> "field": "value"
> }
> },
> "a2": {
> "max": {
> "field": "value.integer"
> }
> }
> }
> }
>
> On Tuesday, December 9, 2014 5:53:19 PM UTC, David Pilato wrote:
>
> > If you want to compute on numerical values, you need to use the right
> > field name.
> > value is a String. So you can’t use it for max agg.
> >
> > You could try with "value.integer". I think it should work.
> >
> > --
> > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)
> > [http://Elasticsearch.com](http://Elasticsearch.com)_
> > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr
> > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs
> > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> >
> > Le 9 déc. 2014 à 18:47, Nuno Lopes [nuno.alexa...@gmail.com](mailto:nuno.alexa...@gmail.com) a écrit :
> >
> > Hello all,
> >
> > Consider the following mapping:
> >
> > PUT /test/value/\_mapping
> > {
> > "properties": {
> > "value": {
> > "type": "string",
> > "index": "analyzed",
> > "index\_analyzer": "standard",
> > "search\_analyzer": "standard",
> > "fields": {
> > "integer": {
> > "type": "integer",
> > "ignore\_malformed": true
> > },
> > "double": {
> > "type": "double",
> > "ignore\_malformed": true
> > },
> > "date": {
> > "type": "date",
> > "ignore\_malformed": true }
> > }
> > }
> > }
> > }
> >
> > with simply these documents:
> >
> > PUT /test/value/1
> >
> > {
> > "value": "v1"
> > }
> > PUT /test/value/2
> > {
> > "value": "2"
> > }
> >
> > Writing this aggregation the whole response consists of a
> > ClassCastException:
> >
> > POST /test/\_search
> > {
> > "aggregations": {
> > "a1": {
> > "terms": {
> > "field": "value"
> > }
> > },
> > "a2": {
> > "max": {
> > "field": "value"
> > }
> > }
> > }
> > }
> >
> > When I'm writing this query I know this is the case but in my application
> > I'm generating different kinds of aggregations (from which some will give
> > ClassCastExceptions but I have no easy way of knowing which beforehand).
> > Is there a way to ignore an aggregation that is invalid and return the
> > results of the ones which are valid? And similarly, would this work for
> > nested aggregations?
> >
> > ## Thank you, best regards,
> >
> > Nuno Lopes
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > To view this discussion on the web visit
> > [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com)
> > [https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/09b76e9b-e956-4d61-9057-7aa4f655b4bc%40googlegroups.com?utm_medium=email&utm_source=footer)
> > .
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \.
> > To view this discussion on the web visit
> > [https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com)
> > [https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/290e9213-4df1-4383-a15f-4cb9b9c09a1b%40googlegroups.com?utm_medium=email&utm_source=footer)
> > .
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8ef93efd-478c-430f-bd14-6eb2e16cfbc8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ef93efd-478c-430f-bd14-6eb2e16cfbc8%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:44am UTC](https://discuss.elastic.co/t/is-it-possible-to-avoid-ignore-classcastexceptions-in-aggregations/21167/6 "2017-07-06T00:44:41Z")