You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/28 19:35:02 UTC

[jira] [Commented] (NIFI-4437) ConsumeKafka_0_11 does not add attributes to FlowFiles from message headers unless using demarcator

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

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

GitHub user markap14 opened a pull request:

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

    NIFI-4437: When using ConsumeKafka_0_11 and no message demarcator, en…

    …sure that we add FlowFile Attributes for any Message Header that matches the 'Headers to Add as Attributes (Regex)' property
    
    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-4437

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

    https://github.com/apache/nifi/pull/2183.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 #2183
    
----
commit 8f7993db65455d05e6c97b4e542393f7e1d7feb6
Author: Mark Payne <ma...@hotmail.com>
Date:   2017-09-28T19:34:22Z

    NIFI-4437: When using ConsumeKafka_0_11 and no message demarcator, ensure that we add FlowFile Attributes for any Message Header that matches the 'Headers to Add as Attributes (Regex)' property

----


> ConsumeKafka_0_11 does not add attributes to FlowFiles from message headers unless using demarcator
> ---------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-4437
>                 URL: https://issues.apache.org/jira/browse/NIFI-4437
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>
> When using ConsumeKafka_0_11, any header in the Kafka message whose name matches the "Headers to Add as Attributes (Regex)" property should be added to the FlowFile as an attribute. This works properly if the "Message Demarcator" property is set. However, if the property is not set, the attributes are not added.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)