[
https://issues.apache.org/jira/browse/METRON-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356794#comment-16356794
]
ASF GitHub Bot commented on METRON-1397:
----------------------------------------
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/914
@ottobackwards Really want that myth to be a reality... as soon as we can
get the config overwrite problem solved... but this really isn't the ticket to
discuss that on :)
I'm kinda keen on this parser looking at things like CloudTrail logs and
such like which appear with merged JSON right now. The other thing that I think
this would link up to is the idea that's been floating around about chaining
parsers. This parser could well be a split parser, which then routes to other
parsers with different transformations for example depending on the message,
but again, that's deep future and should probably be on a discuss thread about
parser chaining.
> JSONMap parser should support JSON Path expressions to split input into
> multiple messages
> -----------------------------------------------------------------------------------------
>
> Key: METRON-1397
> URL: https://issues.apache.org/jira/browse/METRON-1397
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Major
>
> The parser interface takes byte[] and returns a list<jsonobject>.
> It is consistent with the intent of the interface that any parser may return
> multiple messages from a given byte input.
> For the json map parser, we can make it easier for users (esp. if they do not
> have NiFi ) is we support more intake options out of the box, for instance
> more complex json documents containing lists of items.
> The parser should support a configuration option that declares a jsonpath
> statement, which will be evaluated to yield one or more 'sub' objects to be
> evaluated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
