[jira] [Updated] (FLINK-16332) Support un-ordered mode for async lookup join

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-16332:
-----------------------------------
    Labels: stale-major  (was: )

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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
>              Labels: stale-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)