From issues-return-63879-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Tue Sep 4 04:14:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id AF46B180647 for ; Tue, 4 Sep 2018 04:14:03 +0200 (CEST) Received: (qmail 69141 invoked by uid 500); 4 Sep 2018 02:14:02 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 69132 invoked by uid 99); 4 Sep 2018 02:14:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2018 02:14:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 73443C0558 for ; Tue, 4 Sep 2018 02:14:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id mGtt0n3iwc82 for ; Tue, 4 Sep 2018 02:14:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 178F95F174 for ; Tue, 4 Sep 2018 02:14:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 64D23E00CB for ; Tue, 4 Sep 2018 02:14:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1C11423F98 for ; Tue, 4 Sep 2018 02:14:00 +0000 (UTC) Date: Tue, 4 Sep 2018 02:14:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-5569) Add tags to Route* processors for discoverability MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-5569?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16602= 545#comment-16602545 ]=20 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= =E2=80=A6 =E2=80=A6prove discoverability. =20 Thank you for submitting a contribution to Apache NiFi. =20 In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: =20 ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced= =20 in the commit message? =20 - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA nu= mber you are trying to resolve? Pay particular attention to the hyphen "-" = character. =20 - [x] Has your PR been rebased against the latest commit within the tar= get branch (typically master)? =20 - [x] Is your initial contribution a single, squashed commit? =20 ### 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 li= censed in a way that is compatible for inclusion under [ASF 2.0](http://www= .apache.org/legal/resolved.html#category-a)?=20 - [ ] If applicable, have you updated the LICENSE file, including the m= ain LICENSE file under nifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the ma= in 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? =20 ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in = which it is rendered? =20 ### Note: Please ensure that once the PR is submitted, you check travis-ci for bu= ild 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 =20 ---- commit a4369b0a781fc15ed03438c1bcf4257942c28586 Author: Andy LoPresto Date: 2018-09-04T02:12:56Z NIFI-5569 Added keywords to Route* and ScanAttribute processors to impr= ove 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 & 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*}} processo= rs when trying to detect the presence of some bytes in flowfile content. I = propose adding the keywords "find", "search", "scan", and "detect" to the f= ollowing processors, as they are used for those functions but do not come u= p in a search for those keywords.=20 > * {{RouteOnAttribute}} > * {{RouteOnContent}} > * {{RouteText}} > Additionally, {{ScanContent}} and {{ReplaceText}} can have additional key= words added to improve discoverability.=20 -- This message was sent by Atlassian JIRA (v7.6.3#76005)