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 2020/02/11 02:48:00 UTC

[jira] [Closed] (FLINK-15875) Bump Beam to 2.19.0

     [ https://issues.apache.org/jira/browse/FLINK-15875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dian Fu closed FLINK-15875.
---------------------------
    Resolution: Resolved

Merged to master via:
ef364bbb0b7a73fcbac25f4cc298aea861ad774a
d1bc10f60b7c53a34c4d2192df14f8b5a66868b7

> Bump Beam to 2.19.0
> -------------------
>
>                 Key: FLINK-15875
>                 URL: https://issues.apache.org/jira/browse/FLINK-15875
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Python
>            Reporter: Dian Fu
>            Assignee: Dian Fu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently PyFlink depends on Beam's portability framework for Python UDF execution. The current dependent version is 2.15.0. We should bump it to 2.19.0(the latest version) as it includes several critical features/fixes, e.g.
> 1) BEAM-7951: It allows to not serialize the window/timestamp/pane info between the Java operator and the Python worker which could definitely improve the performance a lot
> 2) BEAM-8935: It allows to fail fast if the Python worker start up failed. Currently it takes 2 minutes to detect the failure if the Python worker is started failed. 
> 3) BEAM-7948: It supports periodically flush the data between the Java operator and the Python worker. This feature is especially useful for streaming jobs and could improve the latency.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)