[C++][Flight] IpcWriteOptions do not appear to be propagated in DoGet requests

[asfimport]

I haven't fully investigated this yet, but I have found that while compression (e.g. ZSTD) is respected in DoPut requests on the client side, it does not appear to propagate through DoGet requests. This may be a bug or by design, but I think it should be possible for the client to request that compression be employed when serving a DoGet

Reporter: Wes McKinney / @wesm

_{Note: This issue was originally created as ARROW-9601. Please see the migration documentation for further details.}

[asfimport]

Wes McKinney / @wesm:
cc @lidavidm in case you know off hand before I go down the rabbit hole

[asfimport]

David Li / @lidavidm:
@wesm the way it was set up, there's no propagation - what the client sets is independent of what the server sets. In this case setting write options for DoGet doesn't make much sense as you're not writing any Arrow data. That is confusing/inconvenient, but building negotiation into Flight is a separate task (did we file a Jira for that/should we just use this one?).

[asfimport]

Wes McKinney / @wesm:
Right, but I didn't see a way to set the IpcWriteOptions for the server side of handling the RPC, or did I miss it? That seems like a functional gap if so

[asfimport]

David Li / @lidavidm:
Ah - RecordBatchStream accepts an IpcWriteOptions.

[asfimport]

David Li / @lidavidm:
Given we've kicked this can down the road a few times: I think we can close it? Compression can be specified server-side, but there's no built-in negotiation (and in ARROW-10351 it's been hard to find a case where compression is beneficial). Or else we can adjust this JIRA to be about implementing negotiation.

[asfimport]

Wes McKinney / @wesm:
Indeed, closing.