[
https://issues.apache.org/jira/browse/HIVE-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185647#comment-17185647
]
gabrywu edited comment on HIVE-16352 at 8/27/20, 6:44 AM:
----------------------------------------------------------
Yes, it's better to repair the Avro files. [~belugabehr], [~navdeepniku]
However, sometimes the Avro files are generated by real-time pipelines, such as
Flink and Spark Streaming. It's difficult to re-generate the Avro files, and
it's OK to discard the bad Avro blocks. In this case, we need a variable which
indicates to skip the bad block.
was (Author: gabry.wu):
Yes, it's better to repair the Avro files.
However, sometimes the Avro files are generated by real-time pipelines, such as
Flink and Spark Streaming. It's difficult to re-generate the Avro files, and
it's OK to discard the bad Avro blocks. In this case, we need a variable which
indicates to skip the bad block.
> 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: 0.5h
> 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)
