Hi! You can use DynamicProcessingTimeSessionWindows with your own SessionWindowTimeGapExtractor implementation. You can count the number of records processed in the extractor and return a time gap of almost zero (but not exactly zero, as it is invalid) if the number of records exceeds the limit.
For more complicated scenarios, you can also write your own window by extending the provided session windows. Prashant Deva <prash...@astradot.com> 于2021年7月28日周三 下午4:08写道： > It seems there is no way to set a maximum size of events for a session > window. > This results in a security vulnerability. > Example: I am recording all the user interaction events of a browser > session. A malicious user can then generate hundreds of thousands or even > millions of events, and cause out of memory errors on our backend. > > I think Session Windows should have a way to stop the window from getting > to an infinite size. >
