Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 89970200D03 for ; Sat, 9 Sep 2017 19:23:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 883D01609B5; Sat, 9 Sep 2017 17:23:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CE0D91609B3 for ; Sat, 9 Sep 2017 19:23:10 +0200 (CEST) Received: (qmail 71706 invoked by uid 500); 9 Sep 2017 17:23:10 -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 71697 invoked by uid 99); 9 Sep 2017 17:23:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Sep 2017 17:23:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8333018D190 for ; Sat, 9 Sep 2017 17:23:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 5L9rmbLl_4ix for ; Sat, 9 Sep 2017 17:23:08 +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 216C55F570 for ; Sat, 9 Sep 2017 17:23:08 +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 CA8A9E00A9 for ; Sat, 9 Sep 2017 17:23:05 +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 F20B524137 for ; Sat, 9 Sep 2017 17:23:02 +0000 (UTC) Date: Sat, 9 Sep 2017 17:23:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-4372) Wait processor - recommend prioritizer in documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 09 Sep 2017 17:23:11 -0000 [ https://issues.apache.org/jira/browse/NIFI-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160017#comment-16160017 ] ASF GitHub Bot commented on NIFI-4372: -------------------------------------- GitHub user pvillard31 opened a pull request: https://github.com/apache/nifi/pull/2139 NIFI-4372 Wait processor - recommend prioritizer in documentation 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-4372 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/2139.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 #2139 ---- commit 87cb16eb73cc10ab5ac6d5346842f03411d86309 Author: Pierre Villard Date: 2017-09-09T17:21:47Z NIFI-4372 Wait processor - recommend prioritizer in documentation ---- > Wait processor - recommend prioritizer in documentation > ------------------------------------------------------- > > Key: NIFI-4372 > URL: https://issues.apache.org/jira/browse/NIFI-4372 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website, Extensions > Reporter: Pierre Villard > Assignee: Pierre Villard > Priority: Trivial > Labels: documentation > > When using the Wait processor, the use of a connection prioritizer (FIFO for instance) on the wait relationship should be recommended in the processor documentation. When having tens of thousands of flow files in the wait relationship, not using a prioritizer could lead to flow files not being released when signal is notified and generate expired flow files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)