[
https://issues.apache.org/jira/browse/ARROW-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482818#comment-17482818
]
Radu Teodorescu commented on ARROW-15473:
-----------------------------------------
Cancel is certainly helpful (assuming it does a direct client side disconnect
and release the threads blocked on read).
The scenario I was having in mind is one where the same connection is shared by
multiple objects potentially outside of the control of the client shutdown,
For example imagine a number of worker threads processing some long lived
streams with arbitrary termination logic and we just want to have a central
"red button" call that terminates the FlightConnection and that automatically
disconnects all those streams (just like having a number of threads sharing the
same TCP connection - when the connection goes down they are all disconnected).
> [C++][FlightRPC] Expose a way to terminate DoExchange stream client side
> ------------------------------------------------------------------------
>
> Key: ARROW-15473
> URL: https://issues.apache.org/jira/browse/ARROW-15473
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++, FlightRPC
> Reporter: Rok Mihevc
> Priority: Major
>
> We want a mechanism to close DoExchange streams from client side in case of
> long running connections. This would be handy for testing and in case e.g.
> user wants to disconnect.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
