Large number handling in KQL

[Bargs]

When a user tries to search for a number larger than Javascript can handle KQL will silently send the wrong query too Elasticsearch. This is worse than throwing an error since the user has no idea something is going wrong and they're getting incorrect results. If nothing else, we should display a helpful error that explains there is a problem and it can be worked around by surrounding the number in double quotes. Lucene doesn't have this issue because Kibana does not parse it and instead treats the whole query as a string. So we could also think about whether it's possible to handle this for the user automatically by treating large numbers as strings in KQL.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[timroes]

Do we have any logic on the value, why we parse it into a number on JS side? Otherwise I would agree with you, it might be better if we keep it as a string, and if there is no logic we do at the number at all, we could consider doing the same for all numbers not just > Number.MAX_SAFE_INTEGER?

[Bargs]

At the moment I don't believe we have any logic on the number value, but I'd have to go through the exercise of changing it to be sure. And yeah, agreed that it would be simpler to treat all the numbers as strings if possible.

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)