RE: Weird ListFile Issue
Yep exactly. It probably shouldn’t do anything if its null or empty.
From: Andrew Grande
Sent: Friday, March 22, 2019 5:04 PM
To: users@nifi.apache.org
Subject: Re: Weird ListFile Issue
[CAUTION: This email originated from outside of Kodak Alaris. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.]
Looks like the processor started listing CWD
On Fri, Mar 22, 2019, 2:00 PM William Gosse
mailto:william.go...@aifoundry.com>> wrote:
The real var name was aimuploaddir and the error was aimduploaddir. Think I
have a work around to prevent the tragedy was wiping out Nifi. I did this:
${aimuploaddir:replaceEmpty('')}
From: Joe Witt mailto:joe.w...@gmail.com>>
Sent: Friday, March 22, 2019 4:06 PM
To: users@nifi.apache.org<mailto:users@nifi.apache.org>
Subject: Re: Weird ListFile Issue
[CAUTION: This email originated from outside of Kodak Alaris. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.]
William
What was the real dir name vs the erroneous name? What might happens depends
on many factors such as os behaviors.
thanks
On Fri, Mar 22, 2019, 12:47 PM William Gosse
mailto:william.go...@aifoundry.com>> wrote:
I ran into kind of a weird issue with the ListFile processor. I was
referencing a variable for my input directory and had enter the variable name
incorrectly.
So I assumed that the with my incorrect variable name the value of the Input
Directory would be null or an empty string.
When I started the InputFile it started listing all the files inside of my Nifi
install directory. Things got bad when the my FetchFile started to delete
them.
I'm on 1.9.1 but I was wondering if this was the normal behavior or some kind
of bug.
If anyone has seen this behavior and has some kind of viable workaround please
let me know.
Re: Weird ListFile Issue
Looks like the processor started listing CWD
On Fri, Mar 22, 2019, 2:00 PM William Gosse
wrote:
> The real var name was aimuploaddir and the error was aimduploaddir. Think
> I have a work around to prevent the tragedy was wiping out Nifi. I did this:
>
> ${aimuploaddir:replaceEmpty('')}
>
>
>
>
>
> *From:* Joe Witt
> *Sent:* Friday, March 22, 2019 4:06 PM
> *To:* users@nifi.apache.org
> *Subject:* Re: Weird ListFile Issue
>
>
>
> [CAUTION: This email originated from outside of Kodak Alaris. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.]
> --
>
> William
>
>
>
> What was the real dir name vs the erroneous name? What might happens
> depends on many factors such as os behaviors.
>
>
>
> thanks
>
>
>
> On Fri, Mar 22, 2019, 12:47 PM William Gosse
> wrote:
>
> I ran into kind of a weird issue with the ListFile processor. I was
> referencing a variable for my input directory and had enter the variable
> name incorrectly.
>
> So I assumed that the with my incorrect variable name the value of the
> Input Directory would be null or an empty string.
>
> When I started the InputFile it started listing all the files inside of my
> Nifi install directory. Things got bad when the my FetchFile started to
> delete them.
>
> I'm on 1.9.1 but I was wondering if this was the normal behavior or some
> kind of bug.
>
> If anyone has seen this behavior and has some kind of viable workaround
> please let me know.
>
>
RE: Weird ListFile Issue
The real var name was aimuploaddir and the error was aimduploaddir. Think I
have a work around to prevent the tragedy was wiping out Nifi. I did this:
${aimuploaddir:replaceEmpty('')}
From: Joe Witt
Sent: Friday, March 22, 2019 4:06 PM
To: users@nifi.apache.org
Subject: Re: Weird ListFile Issue
[CAUTION: This email originated from outside of Kodak Alaris. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.]
William
What was the real dir name vs the erroneous name? What might happens depends
on many factors such as os behaviors.
thanks
On Fri, Mar 22, 2019, 12:47 PM William Gosse
mailto:william.go...@aifoundry.com>> wrote:
I ran into kind of a weird issue with the ListFile processor. I was
referencing a variable for my input directory and had enter the variable name
incorrectly.
So I assumed that the with my incorrect variable name the value of the Input
Directory would be null or an empty string.
When I started the InputFile it started listing all the files inside of my Nifi
install directory. Things got bad when the my FetchFile started to delete
them.
I'm on 1.9.1 but I was wondering if this was the normal behavior or some kind
of bug.
If anyone has seen this behavior and has some kind of viable workaround please
let me know.
Re: Weird ListFile Issue
William What was the real dir name vs the erroneous name? What might happens depends on many factors such as os behaviors. thanks On Fri, Mar 22, 2019, 12:47 PM William Gosse wrote: > I ran into kind of a weird issue with the ListFile processor. I was > referencing a variable for my input directory and had enter the variable > name incorrectly. > > So I assumed that the with my incorrect variable name the value of the > Input Directory would be null or an empty string. > > When I started the InputFile it started listing all the files inside of my > Nifi install directory. Things got bad when the my FetchFile started to > delete them. > > I'm on 1.9.1 but I was wondering if this was the normal behavior or some > kind of bug. > > If anyone has seen this behavior and has some kind of viable workaround > please let me know. > >
Weird ListFile Issue
I ran into kind of a weird issue with the ListFile processor. I was referencing a variable for my input directory and had enter the variable name incorrectly. So I assumed that the with my incorrect variable name the value of the Input Directory would be null or an empty string. When I started the InputFile it started listing all the files inside of my Nifi install directory. Things got bad when the my FetchFile started to delete them. I'm on 1.9.1 but I was wondering if this was the normal behavior or some kind of bug. If anyone has seen this behavior and has some kind of viable workaround please let me know.
