[jira] [Created] (ARROW-9587) [FlightRPC][Java] Clean up DoPut/FlightStream memory handling

["David Li (Jira)" <ji...@apache.org>]

David Li created ARROW-9587:
-------------------------------

             Summary: [FlightRPC][Java] Clean up DoPut/FlightStream memory handling
                 Key: ARROW-9587
                 URL: https://issues.apache.org/jira/browse/ARROW-9587
             Project: Apache Arrow
          Issue Type: Improvement
          Components: FlightRPC, Java
    Affects Versions: 1.0.0
            Reporter: David Li
            Assignee: David Li


We've been running into issues with DoPut in Java. In particular:
 * Closing a FlightStream without draining it should not send a cancellation to the other side. A server will have sent an explicit error message, or will simply just not want to read the entire stream. A client should explicitly cancel/gRPC will cancel for you anyways when  you end the call.
 * The server should not close or clean up anything for you in DoPut (it should act like DoExchange). Otherwise trying to use it with ARROW-9586 becomes impossible (you need to close the FlightStream before ending the call, or you'll close the per-call allocator before you close the FlightStream)

I think this also ties into flakiness in unit tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)