Hi Everyone,
I am trying to execute this simple sessionization pipeline, with the allowed lateness shown below: But heres the problem. I am expecting the event highlighted in red above(e12) , to be collected in the side output as a late event. But it isn't. The event is not printed. Whats interesting is, if I make any one of the following changes, the event e12 is considered late and is printed. 1) Event("u1", "e12", 8L) change to Event("u1", "e12", 7L) 2) allowedLateness(Time.milliseconds(2L)) change to allowedLateness(Time.milliseconds(1L)) 3) Event("u1", "e12", 8L) change to Event("u1", "e12", 7L) AND allowedLateness(Time.milliseconds(2L)) change to allowedLateness(Time.milliseconds(4L)) // or anything less than 7L regards -Indraneel |
Hi Indraneel, In your case, ("u1", "e12", 8L) is not considered late and will go into the session window {e7,e8,e9,e11} (range=11~19). This is because 8+3(session gap) >= 11, the lower bound of the existing session window Regarding your 3 questions: >> 1) Event("u1", "e12", 8L) change to Event("u1", "e12", 7L) 7+3 < 11, so e12 will not go into the session window {e7,e8,e9,e11}. And it will be fired for the lateness. >> 2) allowedLateness(Time.milliseconds(2L)) change to allowedLateness(Time.milliseconds(1L)) Reduce the allowedLateness will cause window {e7,e8} to be fired when e9 arrives. So when e12 arrives, the existing session window is (e9,e11} (range=14~17). e12 will be considered to be late in this case. >> 3) Event("u1", "e12", 8L) change to Event("u1", "e12", 7L) AND allowedLateness(Time.milliseconds(2L)) change to allowedLateness(Time.milliseconds(4L)) The same as case 1). Thanks, Zhu Zhu Indraneel R <[hidden email]> 于2019年9月26日周四 上午2:24写道:
|
Free forum by Nabble | Edit this page |