[
https://issues.apache.org/jira/browse/FLINK-16332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16332:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)
