[
https://issues.apache.org/jira/browse/FLINK-12305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot closed FLINK-12305.
----------------------------------
Resolution: Auto Closed
This issue was labeled "stale-minor" 7 ago and has not received any updates so
I have gone ahead and closed it. If you are still affected by this or would
like to raise the priority of this ticket please re-open, removing the label
"auto-closed" and raise the ticket priority accordingly.
> 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: auto-closed, 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)
