Hi all,

I'd like to start a vote on PIP-484: Expose Window Interface for WindowFunction 
Processing.


Summary:
Pulsar Window Functions currently pass only the full window collection to 
WindowFunction.process(). Internally, WindowManager already tracks newly added 
and expired events on each trigger, but that information is dropped before 
calling the user function. This PIP promotes the existing Window view to the 
public API and adds a default process(Window, WindowContext) overload on 
WindowFunction so
class-based implementations can use getNew() / getExpired() for incremental 
processing, while keeping existing lambda and collection-based implementations 
backward compatible.


PIP PR: https://github.com/apache/pulsar/pull/25967
Discuss thread: https://lists.apache.org/thread/gwfpt27j57vkfgcscrj7yyfn0jdg1oq4


The vote will be open for at least 48 hours.


Thanks,
Dream95

Reply via email to