ording to the history of stream. Once lost, these
> states couldn't be recovered using current Flink(version 1.1.3) window
> checkpoint mechanism.
>
> Syinchwun Leo
>
> -邮件原件-
> 发件人: Aljoscha Krettek [mailto:aljos...@apache.org]
> 发送时间: 2016年11月28日 18:58
> 收
Hi,
this is indeed a bug (though I would see it more as a feature since I think
using the Checkpointed interface there can indeed be problematic, as Till
pointed out). The problem is that the Scala Wrapper functions have to
implement all kinds of interfaces so that they can forward to the wrapped
f
Hi 时某人,
I think you've found an inconsistency in Flink's windowing API (but it's
the same in the Java API). Handling operator state in the context of
windows is a little bit delicate because you could have multiple windows in
flight, though. I've pulled Aljoscha in this thread who is more familiar
Hi all:
I am paying attention to Flink, and encounter a problem about user defined
window with checkpoint. My code like this:
class WindowStatistics extends WindowFunction[Event, Int, Tuple, TimeWindow]
with Checkpointed[Option[Int]]: Unit = {
private var count = 0
override def apply
