Timo Walther created FLINK-39255:
------------------------------------
Summary: Support late data in PTFs
Key: FLINK-39255
URL: https://issues.apache.org/jira/browse/FLINK-39255
Project: Flink
Issue Type: Sub-task
Components: Table SQL / Runtime
Reporter: Timo Walther
Assignee: Timo Walther
Silently dropping records contradicts standard SQL semantics, which are
typically agnostic to event-time lateness. Furthermore, relying on strict
watermarking is often impractical, as watermark strategies are frequently
dictated by upstream teams or are too complex for end-users to manage.
Therefore, the PTF implementer should have the autonomy to decide how to handle
late data. Some might drop, some handle it as a special case, or reroute to a
late data side output. In most of the cases, however, users most likely don’t
care about the data being late as they don’t consider event-time semantics in
their implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
