# \_score:"-Infinity" with version 7.6.2, \_score:null from version 6.8.2

**URL:** <https://discuss.elastic.co/t/score-infinity-with-version-7-6-2-score-null-from-version-6-8-2/227834>\
**Category:** Elasticsearch\
**Created:** [April 14, 2020, 12:59am UTC](https://discuss.elastic.co/t/score-infinity-with-version-7-6-2-score-null-from-version-6-8-2/227834 "2020-04-14T00:59:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![erik-sigsci](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@erik-sigsci](https://discuss.elastic.co/u/erik-sigsci)\
**Post date:** [April 14, 2020, 12:59am UTC](https://discuss.elastic.co/t/score-infinity-with-version-7-6-2-score-null-from-version-6-8-2/227834/1 "2020-04-14T00:59:07Z")

</div>

Hello! I'm in process of trying to upgrade a production cluster from 6.8.2 to 7.6.2  
Everything looked good, but as soon as one node was v7.6.2, I started to get json parsing errors from the go olivere library.  
It seems our constant score queries which return null for \_score are now getting "-Infinity", which go json parsing doesn't like. This only happens in production; everything is perfectly happy locally.  
Both locally and in prod the jdk being used is the bundled one.  
I could generate the "-Infinity" with a very simple constant score query with one filter and an inverse date sort. The exact same query on the same cluster when there are no v7 nodes returns a null score.  
I can think of several workarounds, but in case this IS a bug I wanted to report it - especially because none of the work arounds I can think of are pretty. Any advice is appreciated!

---

<div class="post-metadata">

**Author:** ![erik-sigsci](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@erik-sigsci](https://discuss.elastic.co/u/erik-sigsci)\
**Post date:** [April 14, 2020, 7:21pm UTC](https://discuss.elastic.co/t/score-infinity-with-version-7-6-2-score-null-from-version-6-8-2/227834/2 "2020-04-14T19:21:42Z")

</div>

I was able to reproduce this in dev today, by doing the following-  
set up a 3 node cluster of 6.8  
replace node 1 with 7.6, same data dir and node name  
-Infinity  
replace node 2 with 7.6  
no -Infinity  
replace node 3 with 7.6  
no -Infinity

My guess right now is that a cluster with a minority of v7 nodes causes this behavior.

---

<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:** [May 12, 2020, 7:21pm UTC](https://discuss.elastic.co/t/score-infinity-with-version-7-6-2-score-null-from-version-6-8-2/227834/3 "2020-05-12T19:21:45Z")

</div>

Closed on May 12, 2020, 7:21pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.