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
Java's Storage Write API streaming writes is broken on Dataflow runner V2 when autosharding is enabled. The Python wrapper uses the Java implementation and runs exclusively on Runner V2.
To provide a workaround and unblock users, we should enable setting a fixed number of shards.
Issue Priority
Priority: 1 (data loss / total loss of function)
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:
ahmedabu98
changed the title
[Bug]: Python's Storage API streaming writes via xlang is broken on Dataflow because it only runs on Runner V2
[Bug]: Python's Storage API streaming exactly-once writes on DataflowV2 is broken with autosharding, and it's the only option available
Sep 21, 2023
What happened?
Java's Storage Write API streaming writes is broken on Dataflow runner V2 when autosharding is enabled. The Python wrapper uses the Java implementation and runs exclusively on Runner V2.
To provide a workaround and unblock users, we should enable setting a fixed number of shards.
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components
The text was updated successfully, but these errors were encountered: