Range filters on scripted fields don't work when bounds aren't explicit

[lukasolson]

1. Create a scripted field of type number
2. Create a bar chart
3. For X-axis, select range aggregation on the scripted field
4. Add another range, but leave at least one of the From/To empty (signifying the range should have either no upper or lower bound)
5. Run the visualization, then click on the bar generated by the above step to create a filter

Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"expression_script_compilation_exception","reason":"Parameter [gte] must be a numeric type"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"apache-logs-2015.07.01","node":"5Ft1n7ZoSFO81zMCSJeiFQ","reason":{"type":"script_exception","reason":"Error during search with inline script [(ln(doc[\"bytes\"].value))>=gte && (ln(doc[\"bytes\"].value))<lt] using lang [expression]","caused_by":{"type":"expression_script_compilation_exception","reason":"Parameter [gte] must be a numeric type"}}}]}}
    at http://localhost:5601/bundles/kibana.bundle.js:94680:39
    at Function.Promise.try (http://localhost:5601/bundles/commons.bundle.js:54485:23)
    at http://localhost:5601/bundles/commons.bundle.js:54454:31
    at Array.map (native)
    at Function.Promise.map (http://localhost:5601/bundles/commons.bundle.js:54453:31)
    at callResponseHandlers (http://localhost:5601/bundles/kibana.bundle.js:94652:23)
    at http://localhost:5601/bundles/kibana.bundle.js:94166:17
    at wrappedCallback (http://localhost:5601/bundles/commons.bundle.js:33417:82)
    at wrappedCallback (http://localhost:5601/bundles/commons.bundle.js:33417:82)
    at http://localhost:5601/bundles/commons.bundle.js:33503:27

I guess it's possible that this is a bug in Elasticsearch.

[rashidkpc]

Seems likely to be an elasticsearch bug?

"root_cause":[{"type":"expression_script_compilation_exception","reason":"Parameter [gte] must be a numeric type"}

Also, if this is only applies when bounds aren't explicit that error message sure doesn't convey that

[rashidkpc]

Er, this is definitely our bug, we create the filters by concatenating a string basically. I bet we're not looking to see if the gte side of the string exists