[
https://issues.apache.org/jira/browse/FLINK-38562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132250#comment-18132250
]
Dian Fu commented on FLINK-38562:
---------------------------------
[~sangkyoonnam] Thanks for the update.
1. For the chaining strategy, could we follow the same approach as Java’s
AsyncWaitOperator? Its factory uses ChainingStrategy.ALWAYS and implements
YieldingOperatorFactory, which allows the job graph generator to prevent
chaining with legacy sources while preserving chaining in other cases. Setting
HEAD unconditionally would also break otherwise valid upstream chaining,
potentially introducing unnecessary task boundaries and communication overhead.
Could you check whether the same mechanism would work for the Python operator?
2. Fixing the embedded converter bug in a separate PR sounds reasonable for me!
> 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)
