Feature: Early Window Expiration with Triggers #1044
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Early Window Expiration with Triggers
This PR adds support for early window expiration via callback triggers for tumbling and hopping windows.
Feature Overview
Windows can now be expired early based on custom logic by providing
before_updateorafter_updatecallbacks when defining a window. When these callbacks returnTrue, the window is immediately expired rather than waiting for its natural expiration time.API
Two new optional parameters added to
tumbling_window()andhopping_window():before_update: Callback invoked before updating the window stateafter_update: Callback invoked after updating the window stateBoth callbacks receive:
(aggregated, value, key, timestamp, headers) -> boolExamples
After Update - Expire when sum exceeds threshold:
Before Update - Prevent value from exceeding threshold:
With collect operations:
Implementation Details
.sum(),.mean(), etc.) and.collect()