Abacn opened a new issue, #39446: URL: https://github.com/apache/beam/issues/39446
### What happened? When an unbounded source starts empty and returns ProcessContinuation.resume(), Prism re-queues the residual token as a pending element with timestamp TIMESTAMP_MIN_VALUE (1970-01-01). This caps the stage's output watermark at 1970-01-01 and prevents watermark advancement. Consequently, Prism's scheduler (bundleReady()) permanently refuses to execute downstream stateful transforms, causing streaming pipelines to freeze indefinitely even after new data arrives in the source. Resolving the existing TODO https://github.com/apache/beam/blob/f1d9c3e122e210dc1a5dc09beaa2e2d3cc14197b/sdks/go/pkg/beam/runners/prism/internal/engine/elementmanager.go#L926 should fix this deadlock. ### 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 YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [x] Component: Prism Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
