Hi, Elasticsearch tries to be smart about the data types for each field if no explicit mapping has been provided. If you have vastly different data types in your JSON which is being extracted, you should create an explicit index mapping and fix the type of the "result" attribute, see https://www.elastic.co/guide/en/elasticsearch/reference/1.7/indices-templates.html and https://www.elastic.co/guide/en/elasticsearch/reference/1.7/mapping.html for details.
Cheers, Jochen On Wednesday, 30 December 2015 15:02:14 UTC+1, [email protected] wrote: > > Hi, > > I think there is a problem using this kind of input from several sources > that "JSON path of data to extract " returns different type of response > (json,text, integer, etc). > > The problem is that the input does not provide the option to define the > name of the variable to save the parsing result from "JSON path of data > to extract ", and always uses the variable "result" to store it.. > > So if the result between two different (and more) inputs, is to different > type Graylog generates a "NumberFormatException" : > > MapperParsingException[failed to parse [result]]; nested: > NumberFormatException[... > > and everything stops working. > > Thank you, > Lefteris. > > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/0161534a-58e5-4fc1-aed3-574672752347%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
