You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/04/07 18:37:41 UTC

[jira] [Updated] (NIFI-3635) ExtractGrok processor gets confused if more than one instance of Processor is on graph

     [ https://issues.apache.org/jira/browse/NIFI-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt updated NIFI-3635:
------------------------------
    Resolution: Fixed
      Assignee: Mark Payne  (was: Joseph Witt)
        Status: Resolved  (was: Patch Available)

+1 merged to master.

> 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: Mark Payne
>            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)