lidavidm commented on issue #3454: URL: https://github.com/apache/arrow-adbc/issues/3454#issuecomment-3341016518
The current design is basically "Send, but not Sync; except if Cancel exists you may call that concurrently". Which is why I've been saying that the separate handle is the most appropriate design in terms of matching the rest of the implementations. That also reduces the restrictions on the Rust side (no need to require Sync; no need to do internal locking, at least for FFI; Rust-native drivers can presumably minimize mutable state to a cancellation token or flag) -- 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]
