# Minor regression with 0.18.5 around handling of Double.NaN

**URL:** <https://discuss.elastic.co/t/minor-regression-with-0-18-5-around-handling-of-double-nan/6066>\
**Category:** Elasticsearch\
**Created:** [December 5, 2011, 9:35am UTC](https://discuss.elastic.co/t/minor-regression-with-0-18-5-around-handling-of-double-nan/6066 "2011-12-05T09:35:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jan\_Fiedler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jan_fiedler/32/2518_2.png) [@Jan\_Fiedler](https://discuss.elastic.co/u/Jan_Fiedler)\
**Post date:** [December 5, 2011, 9:35am UTC](https://discuss.elastic.co/t/minor-regression-with-0-18-5-around-handling-of-double-nan/6066/1 "2011-12-05T09:35:03Z")

</div>

I upgraded to 0.18.5 (from 0.18.4) and my test cases show a minor  
regression around Double.NaN handling. My test indexes a couple of  
documents with different Double values (null and NaN among them). The test  
that turned read is a matchAllQuery with a missingFilter. With 0.18.4 this  
test only identified documents that really have 'null' as double value.  
With 0.18.5 this test also returns documents that have Double.NaN. Is this  
behavior change intended (couldn't find a matching issue in the release  
notes)?

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [December 5, 2011, 7:29pm UTC](https://discuss.elastic.co/t/minor-regression-with-0-18-5-around-handling-of-double-nan/6066/2 "2011-12-05T19:29:14Z")

</div>

It might relate to a change in Lucene and handling NaN numeric values, I  
don't know the specifics exactly, need to check it out.

On Mon, Dec 5, 2011 at 11:35 AM, Jan Fiedler [fiedler.jan@gmail.com](mailto:fiedler.jan@gmail.com) wrote:

> I upgraded to 0.18.5 (from 0.18.4) and my test cases show a minor  
> regression around Double.NaN handling. My test indexes a couple of  
> documents with different Double values (null and NaN among them). The test  
> that turned read is a matchAllQuery with a missingFilter. With 0.18.4 this  
> test only identified documents that really have 'null' as double value.  
> With 0.18.5 this test also returns documents that have Double.NaN. Is this  
> behavior change intended (couldn't find a matching issue in the release  
> notes)?

---

<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:46am UTC](https://discuss.elastic.co/t/minor-regression-with-0-18-5-around-handling-of-double-nan/6066/3 "2017-07-06T03:46:21Z")

</div>

Closed on July 6, 2017, 3:46am UTC