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
Current initialization of FileSystems through FileSystems.setDefaultPipelineOptions is problematic and prone to race conditions, especially when triggered on deserialization of SerializablePipelineOptions (see #18430, BEAM-14465, BEAM-14355).
Particularly with S3FileSystem this is bad as it can easily leak resources (threads!) if used this way (see #26321).
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?
Current initialization of FileSystems through
FileSystems.setDefaultPipelineOptions
is problematic and prone to race conditions, especially when triggered on deserialization ofSerializablePipelineOptions
(see #18430, BEAM-14465, BEAM-14355).Particularly with
S3FileSystem
this is bad as it can easily leak resources (threads!) if used this way (see #26321).Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: