# Script score expressions in Elasticsearch 1.4
**URL:** https://discuss.elastic.co/t/script-score-expressions-in-elasticsearch-1-4/27031
**Category:** Elasticsearch
**Created:** [August 7, 2015, 9:06am UTC](https://discuss.elastic.co/t/script-score-expressions-in-elasticsearch-1-4/27031 "2015-08-07T09:06:53Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@sam\_growthintel](https://discuss.elastic.co/u/sam_growthintel)
#### Post date: [August 7, 2015, 9:06am UTC](https://discuss.elastic.co/t/script-score-expressions-in-elasticsearch-1-4/27031/1 "2015-08-07T09:06:53Z")
Hi,
We have a query that uses the function\_score query. Each function in the `functions` array contains a `script_score` object where the `script` value is an integer.
e.g.
```auto
"script_score": {
"script": 0.335
}
```
This works fine in 1.4.1, but upgrading to 1.4.5 causes issues: specifically we get this error:
```auto
QueryParsingException[[test_index] script_score query does not support [script]
```
The error can be worked around by quoting the `script` value, i.e.:
```auto
"script_score": {
"script": "0.335"
}
```
My question is: what change was made to the parsing of scripts in queries and was the change not considered a "breaking change" because using numerical values was never really the way you were supposed to do things?
---
### Author:  [@Andrei\_Stefan](https://discuss.elastic.co/u/Andrei_Stefan)
#### Post date: [August 7, 2015, 9:24am UTC](https://discuss.elastic.co/t/script-score-expressions-in-elasticsearch-1-4/27031/2 "2015-08-07T09:24:47Z")
I think it's this change: [https://github.com/elastic/elasticsearch/pull/7977](https://github.com/elastic/elasticsearch/pull/7977)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:56pm UTC](https://discuss.elastic.co/t/script-score-expressions-in-elasticsearch-1-4/27031/3 "2017-07-05T23:56:52Z")