kou opened a new issue, #34852: URL: https://github.com/apache/arrow/issues/34852
### Describe the enhancement requested Based on the proposal in https://docs.google.com/document/d/1jhPyPZSOo2iy0LqIJVUs9KWPyFULVFJXTILDfkadx2g/edit# . See also the discussion thread: https://lists.apache.org/thread/247z3t06mf132nocngc1jkp3oqglz7jp Currently, the endpoints within a FlightInfo [explicitly have no ordering](https://github.com/apache/arrow/blob/4a5fadbb7200ae71a151841bac3cbf35dac10258/format/Flight.proto#L269-L270): * There is no ordering defined on endpoints. Hence, if the returned * data has an ordering, it should be returned in a single endpoint. This is unnecessarily limiting. Systems can and do implement distributed sorts, but they can’t reflect this in Flight RPC. And users are asking; see this [Stack Overflow question](https://stackoverflow.com/questions/75180268/apache-arrow-flight-getting-sorted-data-from-multiple-endpoints). Proposal: Add a flag to `FlightInfo`: ```protobuf message FlightInfo { // FlightEndpoints are in the same order as the data. bool endpoints_ordered = 6; } ``` If set, the client may assume that the data is sorted in the same order as the endpoints. Otherwise, the client cannot make any assumptions (as before). ### Component(s) C++, FlightRPC -- 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]
