Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
There are some exceptions which would be easier to debug if we had more debug info at hand. For instance, one frequently encountered error when Impala has stale metadata of an ORC file is:
Invalid ORC postscript length
It'd be better to also print the postscript length we read and the file size, so users can know whether the file is corrupt (so need data regeneration) or the metadata is stale (so need refresh).
Also, there are some cases where the same kind of exception results in different messages, eg. in the ColumnReader.cc Decimal64ColumnReader::readBuffer throws
ParseError("bad read in DoubleColumnReader::next()");
on failing to read from the stream while DoubleColumnReader::readByte throws
ParseError("Read past end of stream in Decimal64ColumnReader " + valueStream->getName());
It would be nice to unify these.
Attachments
Issue Links
- Is contained by
-
IMPALA-9175 Revisit the error handling logics in ORC scanner
- In Progress
- links to