[
https://issues.apache.org/jira/browse/FLINK-35972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zakelly Lan resolved FLINK-35972.
---------------------------------
Fix Version/s: 2.0-preview
Resolution: Fixed
> Directly specify key and process runnable in async state execution model
> ------------------------------------------------------------------------
>
> Key: FLINK-35972
> URL: https://issues.apache.org/jira/browse/FLINK-35972
> Project: Flink
> Issue Type: Sub-task
> Reporter: Zakelly Lan
> Assignee: Zakelly Lan
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0-preview
>
>
> In asynchronous execution model (FLIP-425) for state, the key is managed by
> the framework and automatically assigned before {{processElement}} or
> callback running. However in some cases, there should be an internal
> interface that allows to switch key and start a new process with this key. It
> is useful when implementing something like mini-batch, which triggers a batch
> of real logic for gathered elements at one time instead of the
> {{processElement}} for each element.
> Additionally, the processing invoked by this interface should have a higher
> priority than the normal input, as the semantics of this processing method is
> to continue processing the previously half-processed data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
