nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-5569) Add tags to Route* processors for discoverability
Date Tue, 04 Sep 2018 02:14:00 GMT

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

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

GitHub user alopresto opened a pull request:

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

    NIFI-5569 Added keywords to Route* and ScanAttribute processors to im…

    …prove discoverability.
    
    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:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] 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.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically
master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] 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:
    - [x] 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/alopresto/nifi NIFI-5569

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

    https://github.com/apache/nifi/pull/2984.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 #2984
    
----
commit a4369b0a781fc15ed03438c1bcf4257942c28586
Author: Andy LoPresto <alopresto@...>
Date:   2018-09-04T02:12:56Z

    NIFI-5569 Added keywords to Route* and ScanAttribute processors to improve discoverability.

----


> Add tags to Route* processors for discoverability
> -------------------------------------------------
>
>                 Key: NIFI-5569
>                 URL: https://issues.apache.org/jira/browse/NIFI-5569
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Documentation &amp; Website
>    Affects Versions: 1.7.1
>            Reporter: Andy LoPresto
>            Assignee: Andy LoPresto
>            Priority: Trivial
>              Labels: beginner, documentation, keyword, label
>
> In a fit of forgetfulness, I could not remember the {{RouteOn*}} processors when trying
to detect the presence of some bytes in flowfile content. I propose adding the keywords "find",
"search", "scan", and "detect" to the following processors, as they are used for those functions
but do not come up in a search for those keywords. 
> * {{RouteOnAttribute}}
> * {{RouteOnContent}}
> * {{RouteText}}
> Additionally, {{ScanContent}} and {{ReplaceText}} can have additional keywords added
to improve discoverability. 



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

Mime
View raw message