Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
1.1.0, 1.1.1, 1.2.0
-
None
Description
When using Channel.read(), we need to properly handle the return value and account for the case where we've read fewer bytes than expected. There are a few places where we don't do this properly, which may lead to incorrect data truncation in rare circumstances. I've opened a PR to fix this.
Attachments
Issue Links
- is related to
-
SPARK-4105 FAILED_TO_UNCOMPRESS(5) errors when fetching shuffle data with sort-based shuffle
- Resolved
- links to