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

Posted to issues@beam.apache.org by "Anonymous (Jira)" <ji...@apache.org> on 2023/04/13 10:58:00 UTC

[jira] [Updated] (BEAM-7473) Update RestrictionTracker within Python to not be required to be thread safe

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

Anonymous updated BEAM-7473:
----------------------------
    Status: Triage Needed  (was: Resolved)

> Update RestrictionTracker within Python to not be required to be thread safe
> ----------------------------------------------------------------------------
>
>                 Key: BEAM-7473
>                 URL: https://issues.apache.org/jira/browse/BEAM-7473
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core, sdk-py-harness
>            Reporter: Luke Cwik
>            Assignee: Boyuan Zhang
>            Priority: P2
>             Fix For: 2.17.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The commit [https://github.com/apache/beam/commit/8faffb2bcf28ccab5e9a95322743cc60df65077c#diff-ed95abb6bc30a9ed07faef5c3fea93f0] modified the Java SDK removed the need for users to be thread safe and instead made the framework provide the necessary locking around a restriction tracker.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)