[
https://issues.apache.org/jira/browse/NIFI-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871078#comment-17871078
]
David Handermann commented on NIFI-10002:
-----------------------------------------
[~marfil] This is a challenging issue from an implementation point of view
because it falls into the category of component configuration. NiFi Processors
run in the context of the NiFi user, which is the reason these components have
specific required permissions. The current priority seems accurate for now, and
as this has not received additional commentary, it is not likely to be
addressed in the short term.
> FetchFile can delete configuration files
> ----------------------------------------
>
> Key: NIFI-10002
> URL: https://issues.apache.org/jira/browse/NIFI-10002
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Core Framework
> Affects Versions: 1.15.3
> Reporter: Filip Maretić
> Priority: Minor
>
> There could be a possible problem with the NiFi ListFile -> FetchFile
> combination when using variables that do not exist in the ListFile processor.
> Steps to reproduce:
> * configure the ListFile's input directory to some variable that does not
> exist ${foo}
> * connect the ListFile to FetchFile and configure FetchFile to delete files
> * start the processors
> * NiFi resolved the ${foo} to empty String or null (not sure) and starts to
> fetch files from the NiFi working directory
> * NiFi autodigests itself
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
