Stopped our logstash indexer Dropped today's index Altered the template inorder to set type of a specific previous dynamic field as a string type, since it some time caused index to be created with this dynamic fieled as a long and thus maybe gave field type conflicts. Started the logstash indexer G…

Wondering if the BIG_NUMBER is a Kibana issue or ES, any ideas? Kibana 4.5.0 only sees 4 fields as numbers from ES:2.3.1 nodePort number Edit port number Edit time number Edit _score number Edit How could I dig further down to find the data causing this?

Seems to have disappear again after patching all my ES nodes to 2.3.2-1 inlcuding my tribe node on the kibana host :relieved:

A bit to soon to cheer :confused:, it appeared again, hints on how to drill down to figure out why this is triggered appreciated! Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"illegal_state_exception","reason":"No matching token for number_type [BIG_INTEGER]"}],"type":"s…

Nailed it done to documents like this: {"_index":"popserv-2016.05.25","_type":"popserv","_id":"AVTnEhpwWvfOjJPMxwwj","_score":1.2420747, "_source": {"message":"<redacted>","@timestamp":"2016-05-25T08:39:57.292Z","tags":[], "type":"popserv","host":"<redacted>","lglvl":"Note","event":"Pop…

The Mapping API says mbox is a string as expected, but why do a query return unquoted values then... or am I barking up the wrong tree with this BIG_INTEGER though I'm pretty sure it docs like this that break kibana queries... [root@cbdA ~]# curl -XGET 'http://localhost:9200/popserv-2016.05.25/_ma…

If I index a doc and prefix my large number for mbox field with some letters then query API returns a '"' quoted value and thus kibana sees no issue with BIG_INTEGER... seems a bug to me that ES tries to return a number though the type is mapped as a string, just because it see only numbers in the s…

:blush: it's not a ES bug, it's my own mistake, had a logstash filter that splits key/value pairs into fields with this ruby bit: k = kvs[0] v = kvs[1] if v.match('\A\d+\Z') event[k] = v.to_i elsif v.match('\A\d+\.\d+\Z') event[k] = v…

No matching token for number_type [BIG_INTEGER]

Elastic Stack Elasticsearch

Topic		Replies	Views
URLs with ?fields parameter: getting error: No matching token for number_type BIG_INTEGER Elasticsearch	2	712	July 6, 2017
Bigint values in elasticsearch Elasticsearch	2	2920	February 22, 2017
ElasticSearch + CouchDB + BIG_INTEGER = Oh My Elasticsearch	3	446	July 6, 2017
Metricbeat default index template causes "No matching token for number_type [BIG_INTEGER]" Beats metricbeat	6	898	October 15, 2018
No matching token for number_type [BIG_INTEGER] on update Elasticsearch	1	1009	July 5, 2017

No matching token for number_type [BIG_INTEGER]

Related topics