[
https://issues.apache.org/jira/browse/NIFI-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961223#comment-15961223
]
ASF subversion and git services commented on NIFI-3635:
-------------------------------------------------------
Commit a5d630672a7b24ca1f60073182209b998172c0b3 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a5d6306 ]
NIFI-3635: This closes #1631. Avoid using a static member variable for the
'Grok' object. Code cleanup
Signed-off-by: joewitt <[email protected]>
> ExtractGrok processor gets confused if more than one instance of Processor is
> on graph
> --------------------------------------------------------------------------------------
>
> Key: NIFI-3635
> URL: https://issues.apache.org/jira/browse/NIFI-3635
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Joseph Witt
> Priority: Critical
> Fix For: 1.2.0
>
>
> ExtractGrok uses a 'private static final' member variable for the Grok
> object. This means that all instances of the Processor have the same 'Grok'
> object. So if two or more Processors are added to the graph, the Grok
> Expression configured for the last-started Processor is the Expression that
> will be used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
