[
https://issues.apache.org/jira/browse/FLINK-38562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132303#comment-18132303
]
Sangkyoon Nam commented on FLINK-38562:
---------------------------------------
[~dianfu], following {{AsyncWaitOperator}} works here, so I'll drop {{HEAD}}.
The prototype's factory already keeps the default {{ALWAYS}} and implements
{{YieldingOperatorFactory}}, so I compared it with a {{HEAD}} variant and a
variant without the marker on the same local build, at parallelism 1 and
capacity 1. After {{from_collection}}, the async operator isn't chained to the
source and the job finishes; without the marker it's chained and fails with
"Illegal thread detected". After a {{NumberSequenceSource}}, alone or followed
by a thread-mode Python {{map}} or {{ProcessFunction}} side output, each
pipeline stays in one task with the expected values, while {{HEAD}} splits each
into two. In the chained Python cases the operator did yield to the mailbox,
which I checked with temporary logging. I haven't covered checkpoint/restore or
parallelism above 1 yet.
> Support thread mode of async function in Python DataStream API
> ---------------------------------------------------------------
>
> Key: FLINK-38562
> URL: https://issues.apache.org/jira/browse/FLINK-38562
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Reporter: Dian Fu
> Assignee: Sangkyoon Nam
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
