You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2019/04/04 19:54:00 UTC

[jira] [Resolved] (ARROW-4625) [Flight] Wrap server busy-wait methods

     [ https://issues.apache.org/jira/browse/ARROW-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney resolved ARROW-4625.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.14.0

Issue resolved by pull request 4110
[https://github.com/apache/arrow/pull/4110]

> [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: 20m
>  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
(v7.6.3#76005)