[ https://issues.apache.org/jira/browse/METRON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566177#comment-15566177 ]
ASF GitHub Bot commented on METRON-496: --------------------------------------- Github user ottobackwards commented on the issue: https://github.com/apache/incubator-metron/pull/304 two things, if I may comment * did you mean to bring in the CSV parser change? * isn't the benefit of this that you can _remove_ the timestamp injection from the generic parsers and do it in stellar? Why add it into the csv? > Field transformations are applied after parser validation > --------------------------------------------------------- > > Key: METRON-496 > URL: https://issues.apache.org/jira/browse/METRON-496 > Project: Metron > Issue Type: Bug > Affects Versions: 0.2.2BETA > Reporter: Casey Stella > Assignee: Casey Stella > > Field transformations are applied after validation, which means that the > validation cannot be affected by the transformations. Consider a situation > where you get a timestamp field in as a string and the parser validation > expects a long. Conversion could be done as part of a field transformation, > whereas now it would fail validation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)