[
https://issues.apache.org/jira/browse/NIFI-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136058#comment-15136058
]
ASF GitHub Bot commented on NIFI-1483:
--------------------------------------
GitHub user apiri opened a pull request:
https://github.com/apache/nifi/pull/206
NIFI-1483 - ListFile warns of unable to delete old state when there was none
Correcting logic in terms of when local persistence files are removed
during the migration process.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apiri/incubator-nifi nifi-1483
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/206.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 #206
----
commit 869c9a04ee11725ef22c23b69d7df0309ec71b36
Author: Aldrin Piri <[email protected]>
Date: 2016-02-06T23:38:00Z
NIFI-1483 Correcting logic in terms of when local persistence files are
removed during the migration process.
----
> ListFile warns of unable to delete old state when there was none
> ----------------------------------------------------------------
>
> Key: NIFI-1483
> URL: https://issues.apache.org/jira/browse/NIFI-1483
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.5.0
> Reporter: Joseph Witt
> Assignee: Aldrin Piri
> Priority: Minor
> Fix For: 0.5.0
>
>
> Now with the inclusion of NIFI-259 ListFile we have state management.
> ListFile has logic to migrate old state. When you add a new ListFile
> processor to the graph and start pulling data it warns (see attached) that it
> migrated state (but there was none) but that it could delete the old state
> file (but there was none). It should only say this if it actually migrated
> state and actually had trouble deleting an old existing file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
