amoeba commented on issue #38617: URL: https://github.com/apache/arrow/issues/38617#issuecomment-1899434302
Yeah, I think that's the situation we want to cover here. I was originally thinking this could just be built into FlightClient and not the entire DLL/module: Save the PID when we create a FlightClient, do a PID-check either on every RPC or in a background thread like it appears fsspec does, and raise an Exception when the PID doesn't match. My reasoning for putting the check just in FlightClient was to limit the impact to just where we expect the check to be useful since we the two methods have overhead. Would remembering the PID at DLL load or module import work better? -- 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]
