[ https://issues.apache.org/jira/browse/HIVE-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171316#comment-13171316 ]
Hudson commented on HIVE-2660: ------------------------------ Integrated in Hive-trunk-h0.21 #1153 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1153/]) HIVE-2660 Need better exception handling in RCFile tolerate corruptions mode (Ramkumar Vadali via namit) namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1215226 Files : * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/io/RCFile.java > Need better exception handling in RCFile tolerate corruptions mode > ------------------------------------------------------------------ > > Key: HIVE-2660 > URL: https://issues.apache.org/jira/browse/HIVE-2660 > Project: Hive > Issue Type: Bug > Components: Query Processor > Reporter: Ramkumar Vadali > Assignee: Ramkumar Vadali > Priority: Minor > Attachments: HIVE-2660.1.patch, HIVE-2660.patch > > > The exception handling in nextKeyValueTolerateCorruptions treats IOException > as follows: > - if EOFException, corrupt, can be tolerated > - If CheckSumException, corrupt, can be tolerated > - else not a corruption, re-throw > But the compression code can also throw IOException in case of corruption, > which will get re-thrown in this case. > The correct way of handling IOException is: > - if BlockMissingException, re-throw. > - if not BlockMissingException -> corruption, can be tolerated -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira