GitHub user markap14 opened a pull request:

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

    NIFI-3273: Added nifi-toolkit-flowfile-repo that contains a simple Ja…

    …va class that is capable of recovering a FlowFile Repository manually in 
the case of an operating system crash that results in trailing 0's being dumped 
into the edit logs. Also refactored flowfile repo into some independent modules 
so that it additional capabilities can be added in the future to examine the 
flowfile repo
    
    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/markap14/nifi NIFI-3273

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

    https://github.com/apache/nifi/pull/1611.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 #1611
    
----
commit d87cc3efcc58544e9f2ab67f7a08cd71371d1ceb
Author: Mark Payne <[email protected]>
Date:   2017-03-22T17:08:30Z

    NIFI-3273: Added nifi-toolkit-flowfile-repo that contains a simple Java 
class that is capable of recovering a FlowFile Repository manually in the case 
of an operating system crash that results in trailing 0's being dumped into the 
edit logs. Also refactored flowfile repo into some independent modules so that 
it additional capabilities can be added in the future to examine the flowfile 
repo

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to