[
https://issues.apache.org/jira/browse/HIVE-19807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515742#comment-16515742
]
Peter Vary commented on HIVE-19807:
-----------------------------------
[~belugabehr]: If you take a look at the callers of
{{Utilities.getHeaderCount}} you will see, that these methods expect
IOExceptions if there is a problem reading the files. In some cases they catch
every exception and they are creating an IOException from it anyway, but in
case of {{HiveInputFormat}} we might have some extra surprises... As we see in
the test failure (at least this is my guess :) ):
{code}
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[file_with_header_footer_negative]
(batchId=98)
{code}
Thanks,
Peter
> Add Useful Error Message To Table Header/Footer Parsing
> -------------------------------------------------------
>
> Key: HIVE-19807
> URL: https://issues.apache.org/jira/browse/HIVE-19807
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 3.0.0, 2.3.2
> Reporter: BELUGA BEHR
> Assignee: BELUGA BEHR
> Priority: Minor
> Attachments: HIVE-19807.1.patch, HIVE-19807.2.patch
>
>
> Add some useful logging messages to invalid value parsing of
> {{skip.header.line.count}} and {{skip.footer.line.count}} for better
> troubleshooting.
> Also, parsing error resulted in {{java.io.IOException}} which:
> {quote}
> Signals that an I/O exception of some sort has occurred. This class is the
> general class of exceptions produced by failed or interrupted I/O operations.
> {quote}
> A parsing error is not the result of a failed or interrupted I/O operation so
> I dropped it and replaced with runtime exception {{IllegalArgumentException}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
