lidavidm opened a new issue, #34607: URL: https://github.com/apache/arrow/issues/34607
### Describe the enhancement requested Flight is mostly based around synchronous APIs. This is convenient, but doesn't scale as well. There have been various issues filed and ML questions asked over the years about asynchronous APIs. We should consider adding a set of asynchronous APIs (and hopefully to reduce maintenance, rewriting the synchronous APIs as a layer on top of the asynchronous ones). This will also fit better with recommended usage of gRPC (in Java) and UCX (in C++). Also, this would be a chance to tackle some API improvements: - [ ] #34251 - do not mix error handling and RPC status codes - [ ] Standardizing error code mappings between implementations and related APIs - [ ] Ensuring cancellation and timeouts work everywhere - [ ] Ensuring timeouts can work on a per-message basis for long streaming operations - [ ] Ensuring Ctrl+C works reliably - [ ] Integration with frameworks and language features like asyncio/anyio (Python), virtual threads (Java), coroutines (C++), etc. and concepts like structured concurrency - [ ] Ensuring APIs are more uniform to reduce code duplication/special code paths (timeouts, cancellation, etc. are often handled differently for different APIs) Related issues: - [ ] #34600 - [ ] #34221 - [ ] #21039 - [ ] #16604 ### Component(s) FlightRPC -- 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]
