[jira] [Updated] (FLINK-12305) Table API Clarification

["Konstantin Knauf (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-12305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Knauf updated FLINK-12305:
-------------------------------------
      Labels: pull-request-available stale-assigned  (was: auto-closed pull-request-available stale-assigned)
    Priority: Not a Priority  (was: Minor)

> Table API Clarification
> -----------------------
>
>                 Key: FLINK-12305
>                 URL: https://issues.apache.org/jira/browse/FLINK-12305
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Table SQL / API
>    Affects Versions: 1.8.0
>            Reporter: Alex Barnes
>            Assignee: Fabian Hueske
>            Priority: Not a Priority
>              Labels: pull-request-available, stale-assigned
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> It is not clear from the documentation if late arriving data is correctly handled in the Flink Table/SQL APIs. The documentation makes passing reference to recognizing late arriving data, but does not go into depth as to what kind of triggering/processing can be performed on it 
> [https://ci.apache.org/projects/flink/flink-docs-release-1.8/dev/table/streaming/time_attributes.html#event-time]
> This old email thread on the apache-flink-users mailing list tells a different story - specifically that late arriving data is not supported and DataStream APIs need to be used instead:
> [http://osdir.com/apache-flink-users/msg08110.html]
> Has support been added since that email correspondence? Please consider reducing ambiguity in the documentation and update it to better reflect the current/planned state of support for late arriving data in the Table API.
> Thanks,
> Alex



--
This message was sent by Atlassian Jira
(v8.3.4#803005)