lostluck commented on issue #33623: URL: https://github.com/apache/beam/issues/33623#issuecomment-2599186540
Thank you for filing a clear issue. When you spoke to me offline, it wasn't clear this was a problem on *second* invocations of a pipeline run that caused the problem. ------ I don't see any harm in having the prism process persist. It's set to auto close when Python exits, which is probably a long lived interpreter in this context. But it is a problem that we aren't taking advantage of the existing caching mechanism probably. I think all that we need to do is set a class level handle that keeps the existing server instance on the first startup of prism, and then retain that for subsequent invocations, and it avoids the issue of trying to start a new one. -- 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]
