[
https://issues.apache.org/jira/browse/NIFI-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953538#comment-15953538
]
Mark Payne commented on NIFI-3635:
----------------------------------
[~trixpan] - no worries, you'll catch it next time :) I say that because I've
seen this same bug several times - some member variable is marked static for
some reason (likely out of habit of typing 'static final' for constants), and
all instances of the processor start picking up the same values. It's
definitely easy to miss, though.
> 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)
