carloea2 opened a new issue, #8189: URL: https://github.com/apache/texera/issues/8189
## What happened? The broadcast partitioner stores one shared pending batch, but a targeted flush resets that batch after the first receiver. OutputManager flushes control boundaries one receiver at a time, so only the first receiver receives pending tuples. Later receivers receive the control message without the tuples. Flushing an unknown receiver also clears pending data. Before: flush A sends tuple and marker, then flush B sends only the marker. After: each configured receiver gets the tuple once before the shared batch is cleared. Repeated flushes do not duplicate it, and unknown receivers leave it untouched. ## How to reproduce? 1. Create a BroadcastPartitioner with receivers A and B. 2. Add one tuple below the configured batch size. 3. Flush a control message to A, then flush the same boundary to B. 4. Observe that A receives the tuple and marker while B receives only the marker. 5. Add another pending tuple and flush an unknown receiver. Observe that the tuple is discarded. ## Version/Branch 1.3.0-incubating-SNAPSHOT (main) ## Commit Hash 70c21145887920528d7d5540e3fb790b43e8b759 ## Relevant log output receiver_A=[1, EmbeddedControlMessage] receiver_B=[EmbeddedControlMessage] batch_after_unknown=0 -- 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]
