You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2020/08/26 14:21:00 UTC
[jira] [Commented] (HIVE-16352) Ability to skip or repair out of
sync blocks with HIVE at runtime
[ https://issues.apache.org/jira/browse/HIVE-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185214#comment-17185214 ]
David Mollitor commented on HIVE-16352:
---------------------------------------
I am not in favor of this. The worst kind of Hive error is a query that completes without error but with invalid results. Better to just have the query fail, provide a clear error message and have the operator clear the bad Avro file manually and investigate why the file is corrupt.
> Ability to skip or repair out of sync blocks with HIVE at runtime
> -----------------------------------------------------------------
>
> Key: HIVE-16352
> URL: https://issues.apache.org/jira/browse/HIVE-16352
> Project: Hive
> Issue Type: New Feature
> Reporter: Navdeep Poonia
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a file is corrupted it raises the error java.io.IOException: Invalid sync! with hive.
> Can we have some functionality to skip or repair such blocks at runtime to make avro more error resilient in case of data corruption.
> Error: java.io.IOException: java.io.IOException: java.io.IOException: While processing file s3n://<bucket>/navdeepp/warehouse/avro_test/354dc34474404f4bbc0d8013fc8e6e4b_000042. java.io.IOException: Invalid sync!
> at org.apache.hadoop.hive.io.HiveIOExceptionHandlerChain.handleRecordReaderNextException(HiveIOExceptionHandlerChain.java:121)
> at org.apache.hadoop.hive.io.HiveIOExceptionHandlerUtil.handleRecordReaderNextException(HiveIOExceptionHandlerUtil.java:77)
> at org.apache.hadoop.hive.shims.HadoopShimsSecure$CombineFileRecordReader.doNextWithExceptionHandler(HadoopShimsSecure.java:334)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)