[
https://issues.apache.org/jira/browse/NIFI-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295073#comment-16295073
]
ASF subversion and git services commented on NIFI-4702:
-------------------------------------------------------
Commit 406db4867a60d830218de70e00ad7b9f9686b54a in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=406db48 ]
NIFI-4702: When we check the next line for matches in Grok Reader, store the
Map that is returned so that we don't have to re-evaluate the regexes the next
time that nextRecord() is called
Signed-off-by: Matthew Burgess <[email protected]>
This closes #2349
> Grok Record Reader applies regex to each line twice in some situations
> ----------------------------------------------------------------------
>
> Key: NIFI-4702
> URL: https://issues.apache.org/jira/browse/NIFI-4702
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.5.0
>
>
> When using the Grok Record Reader, it reads the next line from the stream to
> check if it needs to be appended to the record, is the start of a stack
> trace, etc. When this is done, if the next line matches the configured
> pattern, it is stored as 'nextLine' but we don't store the Map that is
> obtained from calling captures(). This means that the next iteration of
> nextRecord() must re-evaluate the regexes against 'nextLine'. We should
> instead just keep the Map as a member variable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
