[
https://issues.apache.org/jira/browse/METRON-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685636#comment-15685636
]
Otto Fowler commented on METRON-583:
------------------------------------
So, here is the problem:
Grok 0.1.0 - if it could parseInteger, it converted to integer
Grok 0.1.3 - if you specify integer, it converts, if you don't it keeps it as
string, thus regression for all of our rules
So this is a lot to chew off.
I have not been able to find anything about a 'breaking change' in java-grok
around this.
I would think for compatibly sake, the old behavior would be kept ( if no
specifier then if int else string )?
> Update GROK to 0.1.3 to support conversion in grok patterns
> -----------------------------------------------------------
>
> Key: METRON-583
> URL: https://issues.apache.org/jira/browse/METRON-583
> Project: Metron
> Issue Type: Bug
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> Some users are having problems when passing in strings that are parsable as
> integer types such as "0003222".
> In this case they want the string "0003222" not 3222.
> The grok pattern language supports type specifications in 0.1.3 which allow
> you to specify in the pattern that you want it as a string explicitly, such as
> %{USERNAME:namefield;string}
> Metron should update to this version and gain that support.
> 0.1.3 is _not_ the latest version, however, but should be close enough to
> hopefully not have any regressions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
