scwhittle opened a new issue, #36470:
URL: https://github.com/apache/beam/issues/36470

   ### What happened?
   
   This shows up in Dataflow as the errors in harness logs:
   `generic::invalid_argument: SDK reported a smaller watermarkhold: 
2025-09-11T02:45:27.292+00:00 than the computed lower bound: 
2025-09-11T02:51:11.775+00:00`
   
   Partitions are added to the metadata table with their start timestamp.  The 
detectnewchangestreams fn outputs new restrictions for these partitions with 
the minimum watermark of all partitions and then during processing of a 
partition the timestamp is strictly increasing.
   
   This was root-caused to possible reordering of updating watermarks in the 
metadata table.  It is exacerbated by watermark caching and filtering that was 
added to change streams in 2.67.
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [x] 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
   - [ ] Component: Samza 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]

Reply via email to