[
https://issues.apache.org/jira/browse/FLINK-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10031:
-----------------------------------
Labels: auto-deprioritized-major stale-major (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Support handling late events in Table API & SQL
> -----------------------------------------------
>
> Key: FLINK-10031
> URL: https://issues.apache.org/jira/browse/FLINK-10031
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Major
> Labels: auto-deprioritized-major, 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)
