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/06/22 16:59:56 UTC

[lazy-consensus vote] NIP-31: Source Backlog Reporting

Team,

I'd like to start a vote thread (with lazy consensus [1]) for NIP-31 [2],
which aims to let source Processors and Connectors report how much
data is still waiting on their source system, surfaced through the
REST API and the UI.

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 has been 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-31

Re: [lazy-consensus vote] NIP-31: Source Backlog Reporting

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

Thanks all, the vote passes! I expect to put together a Pull Request for the API to be reviewed soon.

Thanks
-Mark


> On Jun 22, 2026, at 12:59 PM, Mark Payne <ma...@hotmail.com> wrote:
> 
> Team,
> 
> I'd like to start a vote thread (with lazy consensus [1]) for NIP-31 [2],
> which aims to let source Processors and Connectors report how much
> data is still waiting on their source system, surfaced through the
> REST API and the UI.
> 
> 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 has been 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-31

Re: [lazy-consensus vote] NIP-31: Source Backlog Reporting

Posted by Pierre Villard <pi...@gmail.com>.

+1

Le lun. 22 juin 2026 à 19:00, Mark Payne <ma...@hotmail.com> a écrit :
>
> Team,
>
> I'd like to start a vote thread (with lazy consensus [1]) for NIP-31 [2],
> which aims to let source Processors and Connectors report how much
> data is still waiting on their source system, surfaced through the
> REST API and the UI.
>
> 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 has been 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-31