[
https://issues.apache.org/jira/browse/NIFI-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871085#comment-17871085
]
Joe Witt commented on NIFI-10002:
---------------------------------
[~marfil] I do think a rather easy improvement here is to simply detect the
resulting value of the configured path is an empty string in this processor and
consider that a validation failure. There should be no need that I am aware of
to allow a user to specify an empty string without specifically selecting that
in the UI. If they provided a parameter and it computes to an empty string for
this component - being invalid seems fair.
> 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)
