You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by "David Li (Jira)" <ji...@apache.org> on 2020/04/16 18:04:00 UTC

[jira] [Created] (ARROW-8487) [FlightRPC][C++] Make it possible to target a specific payload size

David Li created ARROW-8487:
-------------------------------

             Summary: [FlightRPC][C++] Make it possible to target a specific payload size
                 Key: ARROW-8487
                 URL: https://issues.apache.org/jira/browse/ARROW-8487
             Project: Apache Arrow
          Issue Type: Improvement
          Components: C++, FlightRPC
            Reporter: David Li


gRPC by default limits message sizes on the wire. While Flight in turn disables these by default, they're still useful to be able to control memory consumption. A well-behaved client/server may wish to split up writes to respect these limits. However, right now, there's no way to measure the memory usage of what you're about to write without serializing it.

With ARROW-5377, we can in theory avoid this by having the writer take control of serialization, producing the IpcPayload, then measuring the size and writing the payload if the size is as desired. However, Flight doesn't provide such a low-level mechanism yet - we'd need to open that up as well.



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