Kenn Knowles
Kenn Knowles
I believe the workaround is "use View.asIterable and take the last element of the iterable when consuming the side input."
I think @reuvenlax did some work to deal with this before.
@zhoufek did you follow up with this, or is it still outstanding?
@johnjcasey are you working on this still?
Can we confirm if this can be reproduced or confirmed data loss? Do we have a pipeline that succeeds but the files are not in the final destination?
Any update here? I suggest downgrade to P2 if we cannot get enough information to reproduce and understand it.
Have we reproduced this?
Is there a hope of a fix for 2.57.0 cherry pick? I would guess this is a longstanding issue so getting it fixed in a very thorough way for 2.58.0...
Another good candidate for deletion
Permared right now