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

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

Github user cestella commented on the issue:

    https://github.com/apache/incubator-metron/pull/261
  
    @ottobackwards Regarding your other question, we mandated that every 
message capture the original message and a timestamp as required fields.  If 
the message doesn't have that, then it fails validation and an error is thrown 
for that message.
    
    Certainly after it's parsed, you can apply a stellar transformation and 
replace the timestamp field with another one using Stellar.
    
    There is currently a bug where we apply stellar transformations AFTER that 
validation happens, so we don't have the ability to specify a timestamp via 
stellar if it is not there already.  If we had that fixed, then we could apply 
the timestamp to the message in stellar, for sure.


> JSON Parser
> -----------
>
>                 Key: METRON-434
>                 URL: https://issues.apache.org/jira/browse/METRON-434
>             Project: Metron
>          Issue Type: New Feature
>    Affects Versions: 0.2.1BETA
>            Reporter: Casey Stella
>            Assignee: Casey Stella
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Create a parser which will take a JSON map in.  
> Inner maps should be handled pluggably by:
> * doing nothing
> * unfolding maps (e.g. `{ "foo" : { "bar" : 7 } }` is transformed into 
> `{"foo.bar" : 7 }`
> * Throwing an exception
> * Dropping the inner map.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to