# With 1.5.0, facet date\_histograms min/max now return Infinity or -Infinity instead of numeric values? **URL:** \ **Category:** Elasticsearch\ **Created:** [April 6, 2015, 2:34pm UTC](https://discuss.elastic.co/t/with-1-5-0-facet-date-histograms-min-max-now-return-infinity-or-infinity-instead-of-numeric-values/23110 "2015-04-06T14:34:49Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Chris\_Neal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_neal/32/3527_2.png) [@Chris\_Neal](https://discuss.elastic.co/u/Chris_Neal)\ **Post date:** [April 6, 2015, 2:34pm UTC](https://discuss.elastic.co/t/with-1-5-0-facet-date-histograms-min-max-now-return-infinity-or-infinity-instead-of-numeric-values/23110/1 "2015-04-06T14:34:49Z")
Hi All, This seems like something that should be communicated somewhere if a type has changed return values. Prior to 1.5.0, facet return values were always numeric, now I'm getting "Infinity" and "-Infinity". See example below: This query: { "facets":{ "0":{ "date\_histogram":{ "key\_field":"@timestamp", "value\_field":"process\_duration", "interval":"1m" }, "global":true, "facet\_filter":{ "fquery":{ "query":{ "filtered":{ "query":{ "query\_string":{ "query":"((\_type:perf\_typeA AND process:SOMETHING) OR (\_type:typeA AND process:SOMETHINGELSE))" } }, "filter":{ "bool":{ "must":[ { "range":{ "@timestamp":{ "from":1428328178982, "to":1428329078982 } } } ] } } } } } } } }, "size":0 } returns this: { "took" : 123, "timed\_out" : false, "\_shards" : { "total" : 6, "successful" : 6, "failed" : 0 }, "hits" : { "total" : 920732, "max\_score" : 0.0, "hits" : [] }, "facets" : { "0" : { "\_type" : "date\_histogram", "entries" : [ { "time" : 1428328140000, "count" : 4, - ``` "min" : "Infinity",* ``` - ``` "max" : "-Infinity",* "total" : 0.0, "total_count" : 0, "mean" : 0.0 }, { "time" : 1428328200000, "count" : 7, "min" : 1538.0, "max" : 1538.0, "total" : 1538.0, "total_count" : 1, "mean" : 1538.0 }, { "time" : 1428328260000, "count" : 10, ``` - ``` "min" : "Infinity",* ``` - ``` "max" : "-Infinity",* "total" : 0.0, "total_count" : 0, "mean" : 0.0 }, { "time" : 1428328320000, "count" : 8, ``` - ``` "min" : "Infinity",* ``` - ``` "max" : "-Infinity",* "total" : 0.0, "total_count" : 0, "mean" : 0.0 }, ``` That now breaks parsers that are expecting numbers, and now getting Strings. I wonder what the reason for this change was? I cannot find it in any release notes. Anyone have any ideas? -- 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/CAND3Dpg6pD6ZJabH%3DTn0UM2k3Hp6wi76R0-ADBUk9BPkFuaHrw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg6pD6ZJabH%3DTn0UM2k3Hp6wi76R0-ADBUk9BPkFuaHrw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Chris\_Neal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_neal/32/3527_2.png) [@Chris\_Neal](https://discuss.elastic.co/u/Chris_Neal)\ **Post date:** [April 6, 2015, 2:44pm UTC](https://discuss.elastic.co/t/with-1-5-0-facet-date-histograms-min-max-now-return-infinity-or-infinity-instead-of-numeric-values/23110/2 "2015-04-06T14:44:05Z")
Ok, after some searching of this group, I found some query results from previous versions that had Infinity/-Infinity as well, so it probably wasn't introduced with 1.5.0. Still curious about why the decision to return Strings in a numeric field though 🙂 Maybe someone knows that answer? Much appreciated. Chris On Mon, Apr 6, 2015 at 9:34 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net) wrote: > Hi All, > > This seems like something that should be communicated somewhere if a type > has changed return values. Prior to 1.5.0, facet return values were always > numeric, now I'm getting "Infinity" and "-Infinity". See example below: > > This query: > > { > "facets":{ > "0":{ > "date\_histogram":{ > "key\_field":"@timestamp", > "value\_field":"process\_duration", > "interval":"1m" > }, > "global":true, > "facet\_filter":{ > "fquery":{ > "query":{ > "filtered":{ > "query":{ > "query\_string":{ > "query":"((\_type:perf\_typeA AND process:SOMETHING) OR > (\_type:typeA AND process:SOMETHINGELSE))" > } > }, > "filter":{ > "bool":{ > "must":[ > { > "range":{ > "@timestamp":{ > "from":1428328178982, > "to":1428329078982 > } > } > } > ] > } > } > } > } > } > } > } > }, > "size":0 > } > > returns this: > > { > "took" : 123, > "timed\_out" : false, > "\_shards" : { > "total" : 6, > "successful" : 6, > "failed" : 0 > }, > "hits" : { > "total" : 920732, > "max\_score" : 0.0, > "hits" : > }, > "facets" : { > "0" : { > "\_type" : "date\_histogram", > "entries" : [ { > "time" : 1428328140000, > "count" : 4, > > - > > ``` > "min" : "Infinity",* > > ``` > > - > > ``` > "max" : "-Infinity",* > "total" : 0.0, > "total_count" : 0, > "mean" : 0.0 > }, { > "time" : 1428328200000, > "count" : 7, > "min" : 1538.0, > "max" : 1538.0, > "total" : 1538.0, > "total_count" : 1, > "mean" : 1538.0 > }, { > "time" : 1428328260000, > "count" : 10, > > ``` > > - > > ``` > "min" : "Infinity",* > > ``` > > - > > ``` > "max" : "-Infinity",* > "total" : 0.0, > "total_count" : 0, > "mean" : 0.0 > }, { > "time" : 1428328320000, > "count" : 8, > > ``` > > - > > ``` > "min" : "Infinity",* > > ``` > > - > > ``` > "max" : "-Infinity",* > "total" : 0.0, > "total_count" : 0, > "mean" : 0.0 > }, > > ``` > > That now breaks parsers that are expecting numbers, and now getting > Strings. I wonder what the reason for this change was? I cannot find it > in any release notes. > > Anyone have any ideas? -- 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/CAND3Dpg3aPxNb38d8qWMz36K\_SYLG\_Z%3DG-D\_EQV2OfYCMRQjsg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K_SYLG_Z%3DG-D_EQV2OfYCMRQjsg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [April 6, 2015, 2:52pm UTC](https://discuss.elastic.co/t/with-1-5-0-facet-date-histograms-min-max-now-return-infinity-or-infinity-instead-of-numeric-values/23110/3 "2015-04-06T14:52:46Z")
In the facet entries, you will receive the default values of min/max if total\_count is 0, and the defaults are java.lang.Double.POSITIVE\_INFINITY and java.lang.Double.NEGATIVE\_INFINITY. That is, ES never updates min/max while processing values, because there are no values. I would recommend to switch to the aggregation framework, since the old facet classes will be dropped from Elasticsearch 2.0 Jörg On Mon, Apr 6, 2015 at 4:44 PM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net) wrote: > Ok, after some searching of this group, I found some query results from > previous versions that had Infinity/-Infinity as well, so it probably > wasn't introduced with 1.5.0. > > Still curious about why the decision to return Strings in a numeric field > though 🙂 > Maybe someone knows that answer? > > Much appreciated. > Chris > > On Mon, Apr 6, 2015 at 9:34 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net) > wrote: > > > Hi All, > > > > This seems like something that should be communicated somewhere if a type > > has changed return values. Prior to 1.5.0, facet return values were always > > numeric, now I'm getting "Infinity" and "-Infinity". See example below: > > > > This query: > > > > { > > "facets":{ > > "0":{ > > "date\_histogram":{ > > "key\_field":"@timestamp", > > "value\_field":"process\_duration", > > "interval":"1m" > > }, > > "global":true, > > "facet\_filter":{ > > "fquery":{ > > "query":{ > > "filtered":{ > > "query":{ > > "query\_string":{ > > "query":"((\_type:perf\_typeA AND process:SOMETHING) OR > > (\_type:typeA AND process:SOMETHINGELSE))" > > } > > }, > > "filter":{ > > "bool":{ > > "must":[ > > { > > "range":{ > > "@timestamp":{ > > "from":1428328178982, > > "to":1428329078982 > > } > > } > > } > > ] > > } > > } > > } > > } > > } > > } > > } > > }, > > "size":0 > > } > > > > returns this: > > > > { > > "took" : 123, > > "timed\_out" : false, > > "\_shards" : { > > "total" : 6, > > "successful" : 6, > > "failed" : 0 > > }, > > "hits" : { > > "total" : 920732, > > "max\_score" : 0.0, > > "hits" : > > }, > > "facets" : { > > "0" : { > > "\_type" : "date\_histogram", > > "entries" : [ { > > "time" : 1428328140000, > > "count" : 4, > > > > - > > > > ``` > > "min" : "Infinity",* > > > > ``` > > > > - > > > > ``` > > "max" : "-Infinity",* > > "total" : 0.0, > > "total_count" : 0, > > "mean" : 0.0 > > }, { > > "time" : 1428328200000, > > "count" : 7, > > "min" : 1538.0, > > "max" : 1538.0, > > "total" : 1538.0, > > "total_count" : 1, > > "mean" : 1538.0 > > }, { > > "time" : 1428328260000, > > "count" : 10, > > > > ``` > > > > - > > > > ``` > > "min" : "Infinity",* > > > > ``` > > > > - > > > > ``` > > "max" : "-Infinity",* > > "total" : 0.0, > > "total_count" : 0, > > "mean" : 0.0 > > }, { > > "time" : 1428328320000, > > "count" : 8, > > > > ``` > > > > - > > > > ``` > > "min" : "Infinity",* > > > > ``` > > > > - > > > > ``` > > "max" : "-Infinity",* > > "total" : 0.0, > > "total_count" : 0, > > "mean" : 0.0 > > }, > > > > ``` > > > > That now breaks parsers that are expecting numbers, and now getting > > Strings. I wonder what the reason for this change was? I cannot find it > > in any release notes. > > > > Anyone have any ideas? > > -- > 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/CAND3Dpg3aPxNb38d8qWMz36K\_SYLG\_Z%3DG-D\_EQV2OfYCMRQjsg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K_SYLG_Z%3DG-D_EQV2OfYCMRQjsg%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K\_SYLG\_Z%3DG-D\_EQV2OfYCMRQjsg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K_SYLG_Z%3DG-D_EQV2OfYCMRQjsg%40mail.gmail.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/CAKdsXoH%2BFKHhhKFyArvdYXNKY%2BNds0BX5Hm4YkTWafa4gi9czQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH%2BFKHhhKFyArvdYXNKY%2BNds0BX5Hm4YkTWafa4gi9czQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Chris\_Neal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_neal/32/3527_2.png) [@Chris\_Neal](https://discuss.elastic.co/u/Chris_Neal)\ **Post date:** [April 6, 2015, 3:18pm UTC](https://discuss.elastic.co/t/with-1-5-0-facet-date-histograms-min-max-now-return-infinity-or-infinity-instead-of-numeric-values/23110/4 "2015-04-06T15:18:23Z")
Ah. Understood. Thank you for the clarification! On Mon, Apr 6, 2015 at 9:52 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<[joergprante@gmail.com](mailto:joergprante@gmail.com) > wrote: > In the facet entries, you will receive the default values of min/max if > total\_count is 0, and the defaults are java.lang.Double.POSITIVE\_INFINITY > and java.lang.Double.NEGATIVE\_INFINITY. That is, ES never updates min/max > while processing values, because there are no values. > > I would recommend to switch to the aggregation framework, since the old > facet classes will be dropped from Elasticsearch 2.0 > > Jörg > > On Mon, Apr 6, 2015 at 4:44 PM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net) > wrote: > > > Ok, after some searching of this group, I found some query results from > > previous versions that had Infinity/-Infinity as well, so it probably > > wasn't introduced with 1.5.0. > > > > Still curious about why the decision to return Strings in a numeric field > > though 🙂 > > Maybe someone knows that answer? > > > > Much appreciated. > > Chris > > > > On Mon, Apr 6, 2015 at 9:34 AM, Chris Neal [chris.neal@derbysoft.net](mailto:chris.neal@derbysoft.net) > > wrote: > > > > > Hi All, > > > > > > This seems like something that should be communicated somewhere if a > > > type has changed return values. Prior to 1.5.0, facet return values were > > > always numeric, now I'm getting "Infinity" and "-Infinity". See example > > > below: > > > > > > This query: > > > > > > { > > > "facets":{ > > > "0":{ > > > "date\_histogram":{ > > > "key\_field":"@timestamp", > > > "value\_field":"process\_duration", > > > "interval":"1m" > > > }, > > > "global":true, > > > "facet\_filter":{ > > > "fquery":{ > > > "query":{ > > > "filtered":{ > > > "query":{ > > > "query\_string":{ > > > "query":"((\_type:perf\_typeA AND process:SOMETHING) OR > > > (\_type:typeA AND process:SOMETHINGELSE))" > > > } > > > }, > > > "filter":{ > > > "bool":{ > > > "must":[ > > > { > > > "range":{ > > > "@timestamp":{ > > > "from":1428328178982, > > > "to":1428329078982 > > > } > > > } > > > } > > > ] > > > } > > > } > > > } > > > } > > > } > > > } > > > } > > > }, > > > "size":0 > > > } > > > > > > returns this: > > > > > > { > > > "took" : 123, > > > "timed\_out" : false, > > > "\_shards" : { > > > "total" : 6, > > > "successful" : 6, > > > "failed" : 0 > > > }, > > > "hits" : { > > > "total" : 920732, > > > "max\_score" : 0.0, > > > "hits" : > > > }, > > > "facets" : { > > > "0" : { > > > "\_type" : "date\_histogram", > > > "entries" : [ { > > > "time" : 1428328140000, > > > "count" : 4, > > > > > > - > > > > > > ``` > > > "min" : "Infinity",* > > > > > > ``` > > > > > > - > > > > > > ``` > > > "max" : "-Infinity",* > > > "total" : 0.0, > > > "total_count" : 0, > > > "mean" : 0.0 > > > }, { > > > "time" : 1428328200000, > > > "count" : 7, > > > "min" : 1538.0, > > > "max" : 1538.0, > > > "total" : 1538.0, > > > "total_count" : 1, > > > "mean" : 1538.0 > > > }, { > > > "time" : 1428328260000, > > > "count" : 10, > > > > > > ``` > > > > > > - > > > > > > ``` > > > "min" : "Infinity",* > > > > > > ``` > > > > > > - > > > > > > ``` > > > "max" : "-Infinity",* > > > "total" : 0.0, > > > "total_count" : 0, > > > "mean" : 0.0 > > > }, { > > > "time" : 1428328320000, > > > "count" : 8, > > > > > > ``` > > > > > > - > > > > > > ``` > > > "min" : "Infinity",* > > > > > > ``` > > > > > > - > > > > > > ``` > > > "max" : "-Infinity",* > > > "total" : 0.0, > > > "total_count" : 0, > > > "mean" : 0.0 > > > }, > > > > > > ``` > > > > > > That now breaks parsers that are expecting numbers, and now getting > > > Strings. I wonder what the reason for this change was? I cannot find it > > > in any release notes. > > > > > > Anyone have any ideas? > > > > -- > > 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/CAND3Dpg3aPxNb38d8qWMz36K\_SYLG\_Z%3DG-D\_EQV2OfYCMRQjsg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K_SYLG_Z%3DG-D_EQV2OfYCMRQjsg%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K\_SYLG\_Z%3DG-D\_EQV2OfYCMRQjsg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAND3Dpg3aPxNb38d8qWMz36K_SYLG_Z%3DG-D_EQV2OfYCMRQjsg%40mail.gmail.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/CAKdsXoH%2BFKHhhKFyArvdYXNKY%2BNds0BX5Hm4YkTWafa4gi9czQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH%2BFKHhhKFyArvdYXNKY%2BNds0BX5Hm4YkTWafa4gi9czQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH%2BFKHhhKFyArvdYXNKY%2BNds0BX5Hm4YkTWafa4gi9czQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH%2BFKHhhKFyArvdYXNKY%2BNds0BX5Hm4YkTWafa4gi9czQ%40mail.gmail.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/CAND3DphwaCzAwpfTFt5DGPKtGFawkUtOh\_bpDdA9hCPor1Pv%3DA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAND3DphwaCzAwpfTFt5DGPKtGFawkUtOh_bpDdA9hCPor1Pv%3DA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:21am UTC](https://discuss.elastic.co/t/with-1-5-0-facet-date-histograms-min-max-now-return-infinity-or-infinity-instead-of-numeric-values/23110/5 "2017-07-06T00:21:26Z")