I created a pipeline called parse_duration: { "description" : "ParseDuration", "processors": [ { "grok": { "field": "Duration", "patterns": ["%{NUMBER:DrillDuration}"] } } ] } I simulated posting some dummy data while invoking the pipeline: { "docs": [ …

See the grok basics paragraph in the docs. You need to specify the type in addition The syntax for reusing a grok pattern comes in three forms: %{SYNTAX:SEMANTIC} , %{SYNTAX} , %{SYNTAX:SEMANTIC:TYPE} . The TYPE is the type you wish to cast your named field. int , long , double , float …

Grok processor: Expected output to be decimal, but output was string

Elastic Stack Elasticsearch

system (system) Closed June 5, 2019, 8:22am 3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
GROK NUMBER field type creating field as string and not number Logstash	2	9997	September 27, 2017
Using Ingest to parse a double value Elasticsearch	2	795	October 5, 2017
How to get Number type by using Grok Logstash	4	10181	October 25, 2018
Can we specify other data type in grok processor in the future? Elasticsearch	1	412	December 23, 2016
Ingest pipeline to extract data Elasticsearch	4	1585	June 28, 2019

Grok processor: Expected output to be decimal, but output was string

Related topics