[ARROW-4625] [Flight] Wrap server busy-wait methods

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.14.0
• Component/s: FlightRPC
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/21162
• Assignee: David Li
• Reporter: David Li
• Created: 19/Feb/19 13:50
• Updated: 11/Jan/23 07:35
• Resolved: 04/Apr/19 19:53

Description

Right now in Java, you must manually busy-wait in a loop as the gRPC server's awaitTermination method isn't exposed. Conversely, in C+, you have no choice but to busy-wait as starting the server calls awaitTermination for you. Either Java should also wait on the server, or both Java and C+ should expose an explicit operation to wait on the server.

I would prefer the latter as then the Python bindings could choose to manually busy-wait, which would let Ctrl-C work as normal.

Issue Links

• links to: GitHub Pull Request #4110