scwhittle commented on issue #31445: URL: https://github.com/apache/beam/issues/31445#issuecomment-2176687644
I'm not sure why this would have worked and be broken by beam upgrade; it doesn't look safe to do in general. ProcessContext isn't designed to be used outside of the processElement. Runners may reuse or modify it between processElement invocations. Since you are scheduling work asynchronously you copy the element, timestamp into the scheduled futures instead of keeping and using the ProcessContext. You could use @Element etc annotations in your base class and pass explicitly the element, timestamp to your overidden method to avoid the ProcessContext entirely. -- 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]
