You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/06 10:40:00 UTC

[jira] [Updated] (FLINK-10031) Support handling late events in Table API & SQL

     [ 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 auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, 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: Improvement
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)