# date\_histogram rounding and minimum\_number\_should\_match in filter not working

**URL:** <https://discuss.elastic.co/t/date-histogram-rounding-and-minimum-number-should-match-in-filter-not-working/8450>\
**Category:** Elasticsearch\
**Created:** [July 18, 2012, 4:23pm UTC](https://discuss.elastic.co/t/date-histogram-rounding-and-minimum-number-should-match-in-filter-not-working/8450 "2012-07-18T16:23:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sorostaran](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@Sorostaran](https://discuss.elastic.co/u/Sorostaran)\
**Post date:** [July 18, 2012, 4:23pm UTC](https://discuss.elastic.co/t/date-histogram-rounding-and-minimum-number-should-match-in-filter-not-working/8450/1 "2012-07-18T16:23:55Z")

</div>

Recently moved two indexes from our 18.7 cluster to our 19.3 cluster and date\_histogram with rounding such as "day:ceiling" no longer works.

{  
"size": 0,  
"query": {  
"match\_all": { }  
},  
"facets": {  
"uts": {  
"date\_histogram": {  
"field": "uts",  
"interval": "day:ceiling"  
}  
}  
}  
}

This works fine on our 18.7 cluster, but on our 19.3 cluster, we get

NumberFormatException[For input string: "day:ceiling"]

We get the same error on our 19.7 cluster. Without the rounding (just "day" etc.) it works on both clusters.

* * *

Another issue we had with the index transfer was specifying minimum\_number\_should\_match in a bool filter, it works fine on our 18.7 cluster, but gives an error on our 19.3 cluster. The setting works fine in a bool query on both clusters.

Help on this would be much appreciated.

---

<div class="post-metadata">

**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, 3:19am UTC](https://discuss.elastic.co/t/date-histogram-rounding-and-minimum-number-should-match-in-filter-not-working/8450/2 "2017-07-06T03:19:57Z")

</div>