Re: 回复：Is it possible to handle late data when using table API?

Hi Hequn Thanks for the details. I will give it a try. Med venlig hilsen / Best regards Lasse Nedergaard > Den 17. apr. 2019 kl. 04.09 skrev Hequn Cheng : > > Hi Lasse, > > > some devices can deliver data days back in time and I would like to have > > the results as fast as possible. > >

Re: 回复：Is it possible to handle late data when using table API?

Hi Lasse, > some devices can deliver data days back in time and I would like to have the results as fast as possible. What JingsongLee said is correct. However, it's possible to handle your problem with Table API according to your description above. You can use the non-window(or unbounded)

Re: 回复：Is it possible to handle late data when using table API?

Hi Thanks for the fast reply. Unfortunately it not an option as some devices can deliver data days back in time and I would like to have the results as fast as possible. I have to convert my implementation to use streaming API instead. Med venlig hilsen / Best regards Lasse Nedergaard >

回复：Is it possible to handle late data when using table API?

Hi @Lasse Nedergaard, Table API don't have allowedLateness api. But you can set rowtime.watermarks.delay of source to slow down the watermark clock. -- 发件人：Lasse Nedergaard 发送时间：2019年4月16日(星期二) 16:20 收件人：user 主　题：Is it possible