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.