We noticed some behavior where we configured a BaseWindowedBolt as a tumbling 
window with both Count and Duration based policies and expected a Count + 
Time-Based tumbling window, but realized this only gives a Count base tumbling 
window.  This seems like it could be a useful feature to prevent events from 
potentially sitting in a count policy for an indeterminate amount of time 
before the max pending count is reached.  [feature request if this doesn’t 
already exist (couldn’t find it in issues.apache.org after some searching)]

It seems like one would be able to implement a Tumbling Count and Time Based 
Window with the BaseWindowedBolt configuring it as a non-tumbling window with 
Duration and Count settings.  And utilizing the “New” list from the window 
only, or is this assumption wrong?

Cody

Reply via email to