Open usberkeley opened 1 week ago
@hudi-bot run azure
Can a corrupt SizeAwareDataInputStream
be reused in other codes?
Can a corrupt
SizeAwareDataInputStream
be reused in other codes?
A corrupt SizeAwareDataInputStream cannot be used in other code because it lacks robustness. Under boundary conditions, skipBytes may go out of bounds, and APIs like readInt are non-idempotent, posing potential risks.
A corrupt SizeAwareDataInputStream cannot be used in other code
I mean if there is an opportunity for that to happen.
A corrupt SizeAwareDataInputStream cannot be used in other code
I mean if there is an opportunity for that to happen.
Oh, I see now. The current call chain doesn't trigger it; this is just a code optimization PR
Change Logs
Impact
Enhance robustness
Risk level (write none, low medium or high below)
none
Documentation Update
none
Contributor's checklist