You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 major issues with the ArrowStreamReader that are blocking me from using it.
When it reads a batch from a .NET Stream that doesn't return the whole chunk of memory in one "Read" call (like a socket/network stream), it only calls Read once, and then continues on. This is an issue because it has "garbage" at the end of its buffer (which was never written to by the stream), and when attempting to read the next batch, it is in the middle of the previous batch from the .NET Stream. This causes all sorts of issues because it assumes the next 4 bytes are the message length, which it obviously isn't. See the reading code for where it only calls Read once - it should be in a loop.
ArrowStreamReader has a synchronous ReadNextRecordBatch() method - but it throws NotImplementedException. This is necessary when a caller isn't in an async method, they can't/shouldn't call the async API.
Eric Erhardt / @eerhardt: @wesm, @xhochy, @kou - this is a pretty major issue in the C# library that is blocking usage of the Arrow C# library over a network stream. I have a PR up to fix it that has been approved by Stephen Toub. I'm hoping this PR can be merged for the 0.13 release, as it is super important for our usages.
There are 2 major issues with the ArrowStreamReader that are blocking me from using it.
Reporter: Eric Erhardt / @eerhardt
Assignee: Eric Erhardt / @eerhardt
PRs and other links:
Note: This issue was originally created as ARROW-4997. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: