[
https://issues.apache.org/jira/browse/NIFI-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474860#comment-16474860
]
ASF GitHub Bot commented on NIFI-4136:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/1955
@ottobackwards can you compare this against your latest changes and see if
it's still needed?
> GrokReader - Add a failure option to unmatch behavior options
> -------------------------------------------------------------
>
> Key: NIFI-4136
> URL: https://issues.apache.org/jira/browse/NIFI-4136
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> At the moment, when using the GrokReader, if a line does not match the grok
> expression (and is not part of a stack trace), the line can be either ignored
> (the line will be completely skipped) or appended to the last field from the
> previous line.
> In the case where appending is not desired and that data should not be
> ignored/deleted, we should add the option to route the full flow file to the
> failure relationship. This way the flow file could be treated in a different
> way (for example with SplitText and ExtractGrok to isolate the incorrect
> lines and re-route the correct lines back to the Record processors).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
