You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nifi.apache.org by Mark Payne <ma...@hotmail.com> on 2026/09/17 17:11:59 UTC

[lazy-consensus vote] NIP-47: Allow Connectors to more effectively evolve their flows on startup

Team,

I'd like to start a vote thread (with lazy consensus [1]) for NIP-47 [2],
which aims to let Connectors move, filter, transform, or drop FlowFiles
when a new Connector version changes the flow and lays the foundation
in terms of API for future flow evolution that we may need to introduce.

Per our NIP voting policy, this is proposed as a 24-hour vote. I'll leave
this open for 24 hours and, if nobody objects, will consider the NIP
approved.

The actual PR/code change will still go through our normal RTC process.

Thanks
-Mark

[1] https://apache.org/foundation/voting.html#LazyConsensus
[2] https://issues.apache.org/jira/browse/NIP-47

Re: [lazy-consensus vote] NIP-47: Allow Connectors to more effectively evolve their flows on startup

Posted by Kevin Doran <kd...@apache.org>.

+1

On Thu, Sep 17, 2026 at 1:12 PM Mark Payne <ma...@hotmail.com> wrote:
>
> Team,
>
> I'd like to start a vote thread (with lazy consensus [1]) for NIP-47 [2],
> which aims to let Connectors move, filter, transform, or drop FlowFiles
> when a new Connector version changes the flow and lays the foundation
> in terms of API for future flow evolution that we may need to introduce.
>
> Per our NIP voting policy, this is proposed as a 24-hour vote. I'll leave
> this open for 24 hours and, if nobody objects, will consider the NIP
> approved.
>
> The actual PR/code change will still go through our normal RTC process.
>
> Thanks
> -Mark
>
> [1] https://apache.org/foundation/voting.html#LazyConsensus
> [2] https://issues.apache.org/jira/browse/NIP-47

Re: [lazy-consensus vote] NIP-47: Allow Connectors to more effectively evolve their flows on startup

Posted by Mark Payne <ma...@hotmail.com>.

Thanks, all. Given the positive feedback and in the absence of any objections, I’ll consider the lazy consensus vote to ratify NIP-47 successfully closed.

Thanks!
-Mark

> On Sep 17, 2026, at 3:41 PM, David Handermann <ex...@apache.org> wrote:
> 
> +1
> 
> Thanks Mark, the evoleFlow method is more generic, but this looks like
> a good interface foundation for any future types of changes that
> involve moving things around during a Connector-driven flow
> reconfiguration.
> 
> Regards,
> David Handermann
> 
> On Thu, Sep 17, 2026 at 12:12 PM Mark Payne <ma...@hotmail.com> wrote:
>> 
>> Team,
>> 
>> I'd like to start a vote thread (with lazy consensus [1]) for NIP-47 [2],
>> which aims to let Connectors move, filter, transform, or drop FlowFiles
>> when a new Connector version changes the flow and lays the foundation
>> in terms of API for future flow evolution that we may need to introduce.
>> 
>> Per our NIP voting policy, this is proposed as a 24-hour vote. I'll leave
>> this open for 24 hours and, if nobody objects, will consider the NIP
>> approved.
>> 
>> The actual PR/code change will still go through our normal RTC process.
>> 
>> Thanks
>> -Mark
>> 
>> [1] https://apache.org/foundation/voting.html#LazyConsensus
>> [2] https://issues.apache.org/jira/browse/NIP-47

Re: [lazy-consensus vote] NIP-47: Allow Connectors to more effectively evolve their flows on startup

Posted by David Handermann <ex...@apache.org>.

+1

Thanks Mark, the evoleFlow method is more generic, but this looks like
a good interface foundation for any future types of changes that
involve moving things around during a Connector-driven flow
reconfiguration.

Regards,
David Handermann

On Thu, Sep 17, 2026 at 12:12 PM Mark Payne <ma...@hotmail.com> wrote:
>
> Team,
>
> I'd like to start a vote thread (with lazy consensus [1]) for NIP-47 [2],
> which aims to let Connectors move, filter, transform, or drop FlowFiles
> when a new Connector version changes the flow and lays the foundation
> in terms of API for future flow evolution that we may need to introduce.
>
> Per our NIP voting policy, this is proposed as a 24-hour vote. I'll leave
> this open for 24 hours and, if nobody objects, will consider the NIP
> approved.
>
> The actual PR/code change will still go through our normal RTC process.
>
> Thanks
> -Mark
>
> [1] https://apache.org/foundation/voting.html#LazyConsensus
> [2] https://issues.apache.org/jira/browse/NIP-47