Thanks. Using, data streaming. On Wed, 24 Nov 2021 at 20:56, Caizhi Weng <tsreape...@gmail.com> wrote:
> Hi! > > Are you using the datastream API or the table / SQL API? I don't know if > datastream API has this functionality, but in table / SQL API we have the > following configurations [1]. > > - table.exec.emit.late-fire.enabled: Emit window results for late > records; > - table.exec.emit.late-fire.delay: How often shall we emit results for > late records (for example, once per 10 minutes or for every record). > > > [1] > https://github.com/apache/flink/blob/601ef3b3bce040264daa3aedcb9d98ead8303485/flink-table/flink-table-planner/src/main/scala/org/apache/flink/table/planner/plan/utils/WindowEmitStrategy.scala#L214 > > John Smith <java.dev....@gmail.com> 于2021年11月25日周四 上午12:45写道： > >> Hi I understand that when using windows and having set the watermarks and >> lateness configs. That if an event comes late it is lost and we can >> output it to side output. >> >> But wondering is there a way to do it without the loss? >> >> I'm guessing an "all" window with a custom trigger that just fires X >> period and whatever is on that bucket is in that bucket? >> >
