zeroshade commented on issue #40853: URL: https://github.com/apache/arrow/issues/40853#issuecomment-2027725465
Currently, the spec would require you to send a separate DoGet request for each query and have it return the two streams separately. In theory you *could* leverage the multiple `FlightEndpoints` that are returned to be different streams (one stream per table) but that is technically against the current Flight spec which assumes that multiple flight endpoints are pieces of the same result set, and thus should have the same schema. So if you did this it wouldn't necessarily be compatible with many flight clients. So the best options currently are: 1. Use separate DoGet requests that each return their own result stream 2. Propose a change to the Flight spec to allow multiple different data streams identified back from the same FlightInfo object 3. Revive the discussion on allowing schema changes / evolution within a single IPC stream -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
