[
https://issues.apache.org/jira/browse/METRON-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto Fowler updated METRON-583:
-------------------------------
Affects Version/s: 0.3.0
> Update GROK to version of grok that supports PR#60 ( 0.1.5+?)
> -------------------------------------------------------------
>
> Key: METRON-583
> URL: https://issues.apache.org/jira/browse/METRON-583
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> 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.
> There is a problem however: after this new feature is added, integer types
> that would be parsed out from string captures are now NOT parsed out and will
> be strings.
> This regresses many many of our rules and parsers.
> I created a pull request around this issue
> https://github.com/thekrakken/java-grok/pull/60
> If the PR is not accepted, then we will have to re-write our rules to include
> ;TYPE specifiers where we require them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
