[ https://issues.apache.org/jira/browse/ARROW-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rok Mihevc updated ARROW-4625: ------------------------------ External issue URL: https://github.com/apache/arrow/issues/21162 > [Flight] Wrap server busy-wait methods > -------------------------------------- > > Key: ARROW-4625 > URL: https://issues.apache.org/jira/browse/ARROW-4625 > Project: Apache Arrow > Issue Type: Improvement > Components: FlightRPC > Reporter: David Li > Assignee: David Li > Priority: Minor > Labels: pull-request-available > Fix For: 0.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)