# Suddenly need to add track\_scores to queries

**URL:** https://discuss.elastic.co/t/suddenly-need-to-add-track-scores-to-queries/53914
**Category:** Elasticsearch
**Created:** [June 24, 2016, 5:36pm UTC](https://discuss.elastic.co/t/suddenly-need-to-add-track-scores-to-queries/53914 "2016-06-24T17:36:17Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![arustad](https://avatars.discourse-cdn.com/v4/letter/a/dec6dc/32.png) [@arustad](https://discuss.elastic.co/u/arustad)
#### Post date: [June 24, 2016, 5:36pm UTC](https://discuss.elastic.co/t/suddenly-need-to-add-track-scores-to-queries/53914/1 "2016-06-24T17:36:17Z")

</div>

Cluster: 2c4be5

Hello support!

We've been developing against 2.3.3 locally and recently created and deployed our application to your Cloud Service (cluster: 2c4be5, v2.3.3). What I've noticed is that our queries seem to now require 'track\_scores' in order to limit our search results appropriately (we're sorting by published\_at).

With our local install of ES 2.3.3, and setting track\_scores: false or leaving out all together, we receive 34 results. When we set track\_scores: true, we also receive 34 results. In production (in the cluster), if we set track\_scores: false or leave out, we get 2186 results, but if we set track\_scores: true, we get the expected 34.

Here's an example of the query:

```auto
    GET /video_catalogs/catalog_entry/_search?from=0&size=20
    {  
      "track_scores":false,
       "query":{  
          "query_string":{  
             "default_operator":"AND",
             "query":"waterparks OR waterpark"
          }
       },
       "filter":{  
          "and":[  
             {  
                "term":{  
                   "active":true
                }
             },
             {  
                "or":[  
                   {  
                      "range":{  
                         "sunset_at":{  
                            "gt":"2016-06-24T07:10:08.658-07:00"
                         }
                      }
                   },
                   {  
                      "missing":{  
                         "field":"sunset_at"
                      }
                   }
                ]
             },
             {  
                "range":{  
                   "published_at":{  
                      "lte":"2016-06-24T07:10:08-07:00"
                   }
                }
             },
             {  
    
             },
             {  
                "has_parent":{  
                   "type":"video_catalog",
                   "query":{  
                      "filtered":{  
                         "query":{  
                            "match_all":{  
    
                            }
                         },
                         "filter":{  
                            "or":[  
                               {  
                                  "term":{  
                                     "whitelist_size":0
                                  }
                               },
                               {  
                                  "terms":{  
                                     "whitelist":[  
                                        948
                                     ]
                                  }
                               }
                            ]
                         }
                      }
                   }
                }
             },
             {  
                "terms":{  
                   "network_id":[  
                      215
                   ]
                }
             },
             {  
    
             },
             {  
    
             }
          ]
       },
       "sort":[  
          {  
             "published_at":"desc"
          }
       ]
    }`

```

Did this change recently (track\_scores now defaults to false?), or is there some cluster level configuration that we can change?

Thanks for your help!  
Aaron.

---

<div class="post-metadata">

### Author: ![igor\_k](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_k/32/1157_2.png) [@igor\_k](https://discuss.elastic.co/u/igor_k)
#### Post date: [June 27, 2016, 7:50am UTC](https://discuss.elastic.co/t/suddenly-need-to-add-track-scores-to-queries/53914/2 "2016-06-27T07:50:24Z")

</div>

Hi @arustad,

I moved this post to the elasticsearch category as it seems that you should be able to get a better help there. From the cloud perspective we expose the elasticsearch api as is, without modifying it.

Thanks,  
Igor

---

<div class="post-metadata">

### Author: ![arustad](https://avatars.discourse-cdn.com/v4/letter/a/dec6dc/32.png) [@arustad](https://discuss.elastic.co/u/arustad)
#### Post date: [June 29, 2016, 2:48pm UTC](https://discuss.elastic.co/t/suddenly-need-to-add-track-scores-to-queries/53914/3 "2016-06-29T14:48:33Z")

</div>

Thanks @igor_k, I was hoping that since I included a cluster ID that it might get some priority treatment from the Elasticsearch cloud support team.

---

<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 5, 2017, 10:39pm UTC](https://discuss.elastic.co/t/suddenly-need-to-add-track-scores-to-queries/53914/4 "2017-07-05T22:39:31Z")

</div>