You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:01:02 UTC

[jira] [Updated] (BEAM-5521) Cache execution trees in SDK worker

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

Kenneth Knowles updated BEAM-5521:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Cache execution trees in SDK worker
> -----------------------------------
>
>                 Key: BEAM-5521
>                 URL: https://issues.apache.org/jira/browse/BEAM-5521
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-harness
>            Reporter: Robert Bradshaw
>            Priority: P3
>              Labels: portability-flink
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently they are re-constructed from the protos for every bundle, which is expensive (especially for 1-element bundles in streaming flink). 
> Care should be taken to ensure the objects can be re-usued. 



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