[
https://issues.apache.org/jira/browse/FLINK-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336600#comment-17336600
]
Flink Jira Bot commented on FLINK-10031:
----------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Support handling late events in Table API & SQL
> -----------------------------------------------
>
> Key: FLINK-10031
> URL: https://issues.apache.org/jira/browse/FLINK-10031
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Major
> Labels: stale-major
>
> The Table API & SQL drop late events right now. We should offer something
> like a side channel that allows to capture late events for separate
> processing. For example, this could either be simply a table sink or a
> special table (in Table API) derived from the original table that allows
> further processing. The exact design needs to be discussed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
