You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Anand Inguva (Jira)" <ji...@apache.org> on 2022/01/21 21:43:00 UTC

[jira] [Assigned] (BEAM-13595) Disable save_main_session when using cloudpickle

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

Anand Inguva reassigned BEAM-13595:
-----------------------------------

    Assignee: Anand Inguva  (was: Ryan Thompson)

> Disable save_main_session when using cloudpickle
> ------------------------------------------------
>
>                 Key: BEAM-13595
>                 URL: https://issues.apache.org/jira/browse/BEAM-13595
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-py-core
>            Reporter: Ryan Thompson
>            Assignee: Anand Inguva
>            Priority: P3
>
> [save_main_session|https://github.com/apache/beam/blob/17b62ad9e050f80a88793457aee710ea4711d47b/sdks/python/apache_beam/options/pipeline_options.py#L1089] is a flag in the python sdk that is used by the dill library to save all classes/variables/lambas in memory.
>  
> When the cloudpickle library is used, no session is saved (it is a no op). However, if the runner sees the save_main_session option set it may try to access/move/manager the save_main_session saved file.
>  
> To avoid this, when cloudpickle is the main library save_main_session should be false.
>  
> See also:
> https://issues.apache.org/jira/browse/BEAM-13386



--
This message was sent by Atlassian Jira
(v8.20.1#820001)