[GitHub] [nifi] travisneeley opened a new pull request #3541: NIFI-6387 Implemented RetryFlowFile

[GitBox <gi...@apache.org>]

travisneeley opened a new pull request #3541: NIFI-6387 Implemented RetryFlowFile
URL: https://github.com/apache/nifi/pull/3541
 
 
   Thank you for submitting a contribution to Apache NiFi.
   
   Please provide a short description of the PR here:
   
   #### Description of PR
   
   Processor takes a FlowFile. It will then look for a retry attribute on the FlowFile. If none is present or if the designated retry attribute is set and not a number, the retry attribute is set to "1" and passed to a retry relationship.
   A configurable PropertyDescriptor contains the maximum number of times the FlowFile can be retried before being passed to a separate retries exceeded relationship. This PropertyDescriptor should have a validator for allowable positive integers for the retry.
   Processor may also conditionally penalize the FlowFile on the retry relationship.
    
   Many interactions with NiFi request some information from a service and retry if the response isn't explicitly success. While it's quite common to use UpdateAttribute followed by a RouteOnAttribute to do this, there could be value in having a discreet processor for this.
   
   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? _Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not `squash` or use `--force` when pushing to allow for clean monitoring of changes._
   
   ### 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?
   - [x] 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.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services