lidavidm commented on issue #811: URL: https://github.com/apache/arrow-adbc/issues/811#issuecomment-2123711505
> The thing is, you still have some thing you can look at or wait on or poll -- whereas with this low-level C API, you don't have _anything_ if something has gone unexpectedly wrong. But the struct is caller-allocated, right? So the driver can immediately invoke `on_error`. I'm also thinking about other async APIs; gRPC's callback interface for instance also only has a single error path. UCX does let you check for errors 'immediately' but but because it's poll-driven rather than callback-driven that's effectively also a single error path. On the other hand I agree it would be a better developer experience, and probably the caller already has to handle errors for other things, so I suppose I'm not entirely against it, so long as it's stipulated that it should really only be used for immediate validation errors (e.g. an IO error should basically never be returned through the immediate error). -- 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]
