Hi all,
Following up on the PIP-484 discussion. The proposal exposes the incremental window view (getNew/getExpired) via the public org.apache.pulsar.functions.api.Window interface, and extends WindowFunction with a default overload process(Window<Record<X>>, WindowContext) to keep existing WindowFunction implementations fully backward compatible. PIP PR: https://github.com/apache/pulsar/pull/25967 Could Functions maintainers / PMC members please review and comment on the remaining public API details, like: 1) The contract/Javadoc for mutability of Window#get()/getNew()/getExpired() return values. 2) Any remaining compatibility / deployment considerations for existing WindowFunction implementations. If there are no further concerns, I plan to proceed to start the [VOTE] thread. At 2026-06-08 18:50:53, "Dream95" <[email protected]> wrote: >Hi all, >I'd like to start a discussion on PIP-484: Expose Incremental Window Events >via IncrementalWindowFunction. >This proposal adds an IncrementalWindowFunction API so users can process >window events incrementally (onEvict, onTrigger) instead of only receiving >the full window batch on each fire. > > >PIP PR: https://github.com/apache/pulsar/pull/25967 > >Thanks. >
