# Numbers - ignore scientific notation
**URL:** https://discuss.elastic.co/t/numbers-ignore-scientific-notation/277600
**Category:** Elasticsearch
**Created:** [July 1, 2021, 9:42pm UTC](https://discuss.elastic.co/t/numbers-ignore-scientific-notation/277600 "2021-07-01T21:42:01Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@myronuecker](https://discuss.elastic.co/u/myronuecker)
#### Post date: [July 1, 2021, 9:42pm UTC](https://discuss.elastic.co/t/numbers-ignore-scientific-notation/277600/1 "2021-07-01T21:42:01Z")
We have fields that are defined like this:
```auto
"type": "text",
"store": true,
"fields": {
"date": {
"type": "date",
"ignore_malformed": true,
"format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd"
},
"number": {
"type": "scaled_float",
"scaling_factor": 100000.0,
"ignore_malformed": true
},
"raw": {
"type": "keyword"
}
},
```
This works just fine for most data, but has a huge issue if we pass in a string that happens to appear to be in scientific notation. For example, we tried to index a value of "00007E5479206" and ElasticSearch absolutely blows up on that string because it looks like a number.
It appears that what is happening behind the scenes is that it tries to expand it into decimal format with 5 million zeros. On Windows this can take several minutes before it finally fails, but for some reason it works on Linux.
Is there any way to configure the mapping to not try to format that value as a number?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 29, 2021, 9:42pm UTC](https://discuss.elastic.co/t/numbers-ignore-scientific-notation/277600/2 "2021-07-29T21:42:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.