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 2018/01/24 15:21:00 UTC

[jira] [Commented] (NIFI-4814) Add distinctive attribute to S2S reporting tasks

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

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

GitHub user pvillard31 opened a pull request:

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

    NIFI-4814 - Add distinctive attribute to S2S reporting tasks

    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/pvillard31/nifi NIFI-4814

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

    https://github.com/apache/nifi/pull/2431.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 #2431
    
----
commit 00d52220f34213a2b127a48a6a57cb4db5895959
Author: Pierre Villard <pi...@...>
Date:   2018-01-24T15:15:22Z

    NIFI-4814 - Add distinctive attribute to S2S reporting tasks

----


> Add distinctive attribute to S2S reporting tasks
> ------------------------------------------------
>
>                 Key: NIFI-4814
>                 URL: https://issues.apache.org/jira/browse/NIFI-4814
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>
> I'm currently using multiple S2S reporting tasks to send various monitoring data about my workflows. However this forces me to use multiple input ports (one per type of reporting task) as I'm not able to easily distinct what data comes from what reporting task.
> I'd like to add an attribute "reporting.task.name" set to the name of the reporting task when sending flow files via S2S. This way I can use a single input port and then use a RouteOnAttribute processor to split my data based on the reporting task source. The objective to use a single input port is to reduce the number of threads used for S2S operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)