You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dian Fu (Jira)" <ji...@apache.org> on 2021/01/18 05:10:00 UTC
[jira] [Closed] (FLINK-20933) Config Python Operator Use Managed
Memory In Python DataStream
[ https://issues.apache.org/jira/browse/FLINK-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dian Fu closed FLINK-20933.
---------------------------
Fix Version/s: 1.13.0
Assignee: Huang Xingbo
Resolution: Fixed
Fixed in master via e1d98e2d806493ff921b2984ad2a1eb200835c04
> Config Python Operator Use Managed Memory In Python DataStream
> --------------------------------------------------------------
>
> Key: FLINK-20933
> URL: https://issues.apache.org/jira/browse/FLINK-20933
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 1.12.0, 1.13.0
> Reporter: Huang Xingbo
> Assignee: Huang Xingbo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> Now the way to set `Python DataStream Operator` to use managed memory is to set a hook in the `execute` method of `Python StreamExecutionEnvironment` to traverse the `StreamGraph` and set the `Python Operator` to use managed memory.
> But when the user’s job uses `from_data_stream` to convert the `DataStream` to a `Table`, the `TableEnvironment.execute` method is used at the end rather than `StreamExecutionEnvironment.execute`, so the `Python DataStream` related operators will not have `Managed Memory` set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)