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

["Fabian Hueske (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-12305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831479#comment-16831479 ] 

Fabian Hueske commented on FLINK-12305:
---------------------------------------

Thanks for reporting this issue [~WizardOfZot].

Proper support for late arriving data has not been added to the Table API / SQL yet.
The comment was meant to highlight what is possible with event-time support in general, but I certainly see that it is misleading in this context.
I agree that we should rephrase this part.

Thanks,
Fabian

> Table API Clarification
> -----------------------
>
>                 Key: FLINK-12305
>                 URL: https://issues.apache.org/jira/browse/FLINK-12305
>             Project: Flink
>          Issue Type: Improvement
>          Components: Project Website
>    Affects Versions: 1.8.0
>            Reporter: Alex Barnes
>            Priority: Minor
>
> 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
(v7.6.3#76005)