This came up in a Flight/Flight SQL demo a colleague was working on; it was possible to write a batch with a differing schema than what was stated for the stream, which would lead to a decoding failure on the other side. It might be useful in DEBUG mode to DCHECK this and fail-fast.
The error message could also be improved; ArrayLoader.GetBuffer could at least return the index and the actual # of buffers
This came up in a Flight/Flight SQL demo a colleague was working on; it was possible to write a batch with a differing schema than what was stated for the stream, which would lead to a decoding failure on the other side. It might be useful in DEBUG mode to DCHECK this and fail-fast.
The error message could also be improved;
ArrayLoader.GetBuffer
could at least return the index and the actual # of buffersReporter: David Li / @lidavidm
Note: This issue was originally created as ARROW-16625. Please see the migration documentation for further details.