[ 
https://issues.apache.org/jira/browse/METRON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573105#comment-15573105
 ] 

ASF GitHub Bot commented on METRON-496:
---------------------------------------

Github user justinleet commented on the issue:

    https://github.com/apache/incubator-metron/pull/304
  
    I'm +1 by inspection. I'm pretty agnostic on the question of leaving the 
capability in and would be inclined to do what Casey said and add another jira 
if we are interesting removing timestamp handling.


> 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)

Reply via email to