In flight.proto [1] it states that the encoded bytes are as described in
the flatbuffer schema.
```
/*
* Wrap the result of a getSchema call
*/
message SchemaResult {
// schema of the dataset as described in Schema.fbs::Schema.
bytes schema = 1;
}
```
However, both this schema and the schema on the flight info are actually
encoded like an IPC file stream message.
They start with a 4-byte IPC_CONTINUATION_TOKEN, followed by a 4-byte
message size, followed by a Message wrapping a Schema. See [2] and [3] for
evidence in the Java client.
Is this an accidental bug that has propagated to all client implementations?
Or was it intentional and I should submit a PR to update the comments?
Thanks,
Nate
[1] https://github.com/apache/arrow/blob/master/format/Flight.proto#L195
[2]
https://github.com/apache/arrow/blob/master/java/flight/flight-core/src/main/java/org/apache/arrow/flight/FlightInfo.java#L141
[3]
https://github.com/apache/arrow/blob/master/java/vector/src/main/java/org/apache/arrow/vector/ipc/message/MessageSerializer.java#L161
--
