[
https://issues.apache.org/jira/browse/FLINK-12305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329505#comment-17329505
]
Flink Jira Bot commented on FLINK-12305:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: Minor
> Labels: pull-request-available, stale-assigned, stale-minor
> 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)
