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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945832#comment-15945832 ] 

ASF GitHub Bot commented on NIFI-3635:
--------------------------------------

GitHub user markap14 opened a pull request:

    https://github.com/apache/nifi/pull/1631

    NIFI-3635: Avoid using a static member variable for the 'Grok' object…

    …. Code cleanup
    
    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/markap14/nifi NIFI-3635

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1631.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1631
    
----
commit e211c4f471a0e75d5545f6f5a140a4c30dfc8266
Author: Mark Payne <ma...@hotmail.com>
Date:   2017-03-28T19:59:02Z

    NIFI-3635: Avoid using a static member variable for the 'Grok' object. Code cleanup

----


> 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)