Team, I am using HOP window in Table API, I have t...
# troubleshooting
k
Team, I am using HOP window in Table API, I have tried to set slide as 10 minutes and window as 15 minutes but it’s not working for me. Can anyone help?
m
My recommendation would be to check your watermark configuration
And make sure that you either push in data that allows the windows to close, or check things like configuring idleness etc
k
I am getting below error while trying with 15 minute window size and 10 minutes slide Exception in thread "main" org.example.exceptions.SQLParseException: Error in executing SQL query : HOP table function based aggregate requires size must be an integral multiple of slide, but got size 15000 ms and slide 10000 ms
Basically my idea is to achieve latesness in thw window
m
Late events will still be dropped; that’s prior to the windowing even happening
k
No it will not be let’s say my original window is of 10 minute and I want to allow 5 minute lateness Now to achieve this I will have total 15 minute window with 10 minute slide
and I can some check from 10 to 15 minute for timestamp
m
You’re making the assumption that late data will reach the window
But it will already be dropped at the source
k
I am working on processing time FYI
m
With processing time, how will you have late data?
k
Anyhow by previous processing in another env I have some delay in data arrival
Do you think of any other way to handle late event in TUMBLE window?
with SQL
Hey @Martijn Visser Any suggestion do you think?
m
I don't understand how you are thinking about having late data with processing time
k
Issue is because my data is ingesting let's say 10 minutes now user has written 5 minutes winodw. Does event time create 2 winodw of 5 minutes?