You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- since each process picks a different value, the object is not actually shared across processes (a shared instance of the object is instead created for each individual process).
Tag should not be None by default and probably should not even be optional since this is a misleading behavior. Note that this will be a breaking change for some users (if there are any), but those users are probably relying on buggy behavior anyways.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
What happened?
Right now, MultiProcessShared accepts a tag input -
beam/sdks/python/apache_beam/utils/multi_process_shared.py
Line 171 in 1a52deb
When the tag is set to None, it is set to a random value -
beam/sdks/python/apache_beam/utils/multi_process_shared.py
Line 179 in 1a52deb
Tag should not be None by default and probably should not even be optional since this is a misleading behavior. Note that this will be a breaking change for some users (if there are any), but those users are probably relying on buggy behavior anyways.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: