[
https://issues.apache.org/jira/browse/NIFI-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136123#comment-15136123
]
ASF GitHub Bot commented on NIFI-1483:
--------------------------------------
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/206#issuecomment-180928291
@apiri - +1, works great. Only bit of weirdness, if the old state file was
chmod 0400'ed (i.e., only read access) when I launched nifi, it was still
deleted after migration. chattr +i'ing the file kept it from being deleted
though. may be something for the migration guide.
> 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)
