Exclude filter in aggregations only supports syntax for strings

[marius-dr]

Kibana version: 5.4.2

Elasticsearch version: 5.4.2

Server OS version: Windows

Description of the problem including expected versus actual behavior:
An exclude filter in an aggregation will always be treated as a string filter (it will be wrapped in double quotes). It should also be able to accept an array of values, which is the way that's used to filter other types of values, like numbers.

Steps to reproduce:

1. Create a terms aggregation on a numeric field.
2. Add a value in the Exclude filter in the Advanced sub-page in the correct format ( Ex: [404] )

Request is made like this:

 "aggs": {
    "2": {
      "terms": {
        "field": "machine.ram",
        "exclude": "[4297]",
        "size": 5,
        "order": {
          "_count": "desc"
        }
      }
    }
  }

It should be made like this, if it detects that the field is not a String field.

  "aggs": {
    "2": {
      "terms": {
        "field": "machine.ram",
        "exclude": [4297],
        "size": 5,
        "order": {
          "_count": "desc"
        }
      }
    }
  }

Errors in browser console (if relevant):

Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"aggregation_execution_exception","reason":"Aggregation [2] cannot support regular expression style include/exclude settings as they can only be applied to string fields. Use an array of numeric values for include/exclude clauses used to filter numeric fields"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"logstash-0","node":"dfiqFrvgRb2E7WT0xpfHPg","reason":{"type":"aggregation_execution_exception","reason":"Aggregation [2] cannot support regular expression style include/exclude settings as they can only be applied to string fields. Use an array of numeric values for include/exclude clauses used to filter numeric fields"}}]},"status":500}
KbnError@http://localhost:5601/bundles/commons.bundle.js?v=15117:84:19366
RequestFailure@http://localhost:5601/bundles/commons.bundle.js?v=15117:84:20115
callResponseHandlers/<@http://localhost:5601/bundles/kibana.bundle.js?v=15117:28:10894
[2868]/</Promise.try@http://localhost:5601/bundles/commons.bundle.js?v=15117:83:22323
[2868]/</Promise.map/<@http://localhost:5601/bundles/commons.bundle.js?v=15117:83:21682
[2868]/</Promise.map@http://localhost:5601/bundles/commons.bundle.js?v=15117:83:21647
callResponseHandlers@http://localhost:5601/bundles/kibana.bundle.js?v=15117:28:10502
fetchWithStrategy/<@http://localhost:5601/bundles/kibana.bundle.js?v=15117:27:30047
processQueue@http://localhost:5601/bundles/commons.bundle.js?v=15117:38:23621
scheduleProcessQueue/<@http://localhost:5601/bundles/commons.bundle.js?v=15117:38:23888
$eval@http://localhost:5601/bundles/commons.bundle.js?v=15117:39:4607
$digest@http://localhost:5601/bundles/commons.bundle.js?v=15117:39:2343
$apply@http://localhost:5601/bundles/commons.bundle.js?v=15117:39:5026
done@http://localhost:5601/bundles/commons.bundle.js?v=15117:37:25016
completeRequest@http://localhost:5601/bundles/commons.bundle.js?v=15117:37:28702
createHttpBackend/</xhr.onload@http://localhost:5601/bundles/commons.bundle.js?v=15117:37:29634

[blackberryoctopus]

+1 Vote for this improvement.

[timroes]

Closed via #59425