You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/01 13:55:00 UTC
[jira] [Commented] (NIFI-4165) Update NiFi FlowFile Repository
Toolkit to provide ability to remove FlowFiles whose content is missing
[ https://issues.apache.org/jira/browse/NIFI-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382024#comment-16382024 ]
ASF GitHub Bot commented on NIFI-4165:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/2502
NIFI-4165: Added RemoveFlowFilesWithMissingContent.java and associate…
…d helper classes
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-4165
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2502.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 #2502
----
commit 1109ceb33d51815b90067cc078705dd1c91fc596
Author: Mark Payne <ma...@...>
Date: 2017-07-07T16:54:21Z
NIFI-4165: Added RemoveFlowFilesWithMissingContent.java and associated helper classes
----
> Update NiFi FlowFile Repository Toolkit to provide ability to remove FlowFiles whose content is missing
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4165
> URL: https://issues.apache.org/jira/browse/NIFI-4165
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
>
> The FlowFile Repo toolkit has the ability to address issues with flowfile repo corruption due to sudden power loss. Another problem that has been known to occur is if content goes missing from the content repository for whatever reason (say some process deletes some of the files) then the FlowFile Repo can contain a lot of FlowFiles whose content is missing. This causes a lot of problems with stack traces being dumped to logs and the flow taking a really long time to get back to normal. We should update the toolkit to provide a mechanism for pointing to a FlowFile Repo and Content Repo, then writing out a new FlowFile Repo that removes any FlowFile whose content is missing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)