Describe the bug, including details regarding any error messages, version, and platform.
When an Arrow server (specifically a database engine) sends a malformed StringArray where Offsets exceed the DataBuffer capacity, the Go client panics with runtime error: slice bounds out of range.
While the root cause is often on the server side, the Go client lacks an internal safety check to detect these malformed buffers before attempting to access them, causing the entire application to crash.
Context:
We are currently encountering this when streaming large JSON datasets from Doris DB, where occasional corrupted batches cause our entire streaming service to go down. Having a robust Validate() or Verify() method would allow us to log and skip the bad batch rather than crashing.
Component(s)
Parquet
Describe the bug, including details regarding any error messages, version, and platform.
When an Arrow server (specifically a database engine) sends a malformed StringArray where Offsets exceed the DataBuffer capacity, the Go client panics with runtime error: slice bounds out of range.
While the root cause is often on the server side, the Go client lacks an internal safety check to detect these malformed buffers before attempting to access them, causing the entire application to crash.
Context:
We are currently encountering this when streaming large JSON datasets from Doris DB, where occasional corrupted batches cause our entire streaming service to go down. Having a robust Validate() or Verify() method would allow us to log and skip the bad batch rather than crashing.
Component(s)
Parquet