Thanks Jonathan. That works great. I really appreciate your help.

Thanks,
BH

On Mon, Jan 30, 2017 at 4:05 PM, Jonathan Telfer <[email protected]> wrote:

> Hi BH
>
> 2a. Split text processor to turn each line in your input file into its own
> flow file
> 2b. Extract text processor to pull the flow file content into the
> attributes you need for step 3
>
> Jonathan
>
>
>
> > On 30 Jan 2017, at 22:01, Banias H <[email protected]> wrote:
> >
> > I am still pretty new to Nifi and I have a simple use case that I played
> around but couldn't implement in a flow.
> >
> > In a nutshell, an upstream (non-Nifi) process would generate a file that
> contains remote filenames to copy from a remote system to a different
> remote system.
> >
> > My initial plan would be:
> > 1. GetFile to read the file from upstream with filenames in it
> > 2. ??? <unknown steps>
> > 3. FetchSFTP to fetch the file
> > 4. PutFile to store the file
> >
> > I am stuck in step 2. After Step 1, the filenames are in the flowfile.
> But Step 3 is expecting "Remote File" from an attribute, like ${filename}.
> So I don't know how to turn each line in flowfile into an attribute.
> >
> > I would appreciate info on this or better suggestion to do this simple
> use case. Thanks.
> >
> > Regards,
> > BH
>
>

Reply via email to