Processor does not allow an incoming relationship

[scott <tc...@gmail.com>]

Hello community,

I'm looking at using an external table that would be used to configure 
various NiFi flows by reading the columns from the table and converting 
them into attributes. The idea breaks down with some processors that do 
not allow an incoming relationship, such as ListSFTP, so I can't use 
attributes to control them. Is there any way around this, short of 
modifying the processor code and creating a new custom processor? Is 
there a way to convert the records from the table into variables instead?


Thanks for any help,

Scott

Re: Processor does not allow an incoming relationship

[scott <tc...@gmail.com>]

Thanks Mike. That's what I thought. I'd rather not have to customize the 
processors for this. What about the new variables feature? Is there a 
way to update variables through the API?



On 03/19/2018 04:41 AM, Mike Thomsen wrote:
> Scott,
>
> The "input requirement" is hard-coded into the processor. Not knowing 
> much about your use case, I'd say you're either going to have to get 
> really creative or ask for some changes.
>
> Thanks,
>
> Mike
>
> On Sun, Mar 18, 2018 at 9:37 PM, scott <tcots8888@gmail.com 
> <ma...@gmail.com>> wrote:
>
>     Hello community,
>
>     I'm looking at using an external table that would be used to
>     configure various NiFi flows by reading the columns from the table
>     and converting them into attributes. The idea breaks down with
>     some processors that do not allow an incoming relationship, such
>     as ListSFTP, so I can't use attributes to control them. Is there
>     any way around this, short of modifying the processor code and
>     creating a new custom processor? Is there a way to convert the
>     records from the table into variables instead?
>
>
>     Thanks for any help,
>
>     Scott
>
>

Re: Processor does not allow an incoming relationship

[Mike Thomsen <mi...@gmail.com>]

Scott,

The "input requirement" is hard-coded into the processor. Not knowing much
about your use case, I'd say you're either going to have to get really
creative or ask for some changes.

Thanks,

Mike

On Sun, Mar 18, 2018 at 9:37 PM, scott <tc...@gmail.com> wrote:

> Hello community,
>
> I'm looking at using an external table that would be used to configure
> various NiFi flows by reading the columns from the table and converting
> them into attributes. The idea breaks down with some processors that do not
> allow an incoming relationship, such as ListSFTP, so I can't use attributes
> to control them. Is there any way around this, short of modifying the
> processor code and creating a new custom processor? Is there a way to
> convert the records from the table into variables instead?
>
>
> Thanks for any help,
>
> Scott
>
>