[
https://issues.apache.org/jira/browse/FLINK-16332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-16332:
-------------------------------
Component/s: (was: Table SQL / Planner)
(was: Table SQL / API)
Table SQL / Runtime
> Support un-ordered mode for async lookup join
> ---------------------------------------------
>
> Key: FLINK-16332
> URL: https://issues.apache.org/jira/browse/FLINK-16332
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Runtime
> Reporter: Jark Wu
> Priority: Major
>
> Currently, we only support "ordered" mode for async lookup join. Because the
> ordering in streaming SQL is very important, the accumulate and retract
> messages shoudl be in ordered. If messages are out of order, the result will
> be wrong.
> The "un-ordered" mode can be enabled by a job configuration. But it will be a
> prefered option. Only if it doesn't affect the order of acc/retract messages
> (e.g. it is just an append-only stream), the "un-ordered" mode will be
> enabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
