[
https://issues.apache.org/jira/browse/HBASE-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doğacan Güney updated HBASE-1627:
---------------------------------
Attachment: tableinput.patch
A simple patch to change catch clause to catch all IOException-s. Are there any
downsides to this? If an IOException is thrown, reset your scanner, try again
and if it fails again your job fails. Makes sense to me :D
> TableInputFormatBase#nextKeyValue catches the wrong exception
> -------------------------------------------------------------
>
> Key: HBASE-1627
> URL: https://issues.apache.org/jira/browse/HBASE-1627
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Doğacan Güney
> Priority: Minor
> Attachments: tableinput.patch
>
>
> TableInputFormatBase#nextKeyValue only catches UnknownScannerException from
> Scanner.next. However, scanner may throw other exceptions:
> {code}
> /* from HTable.ClientScanner#next */
> try {
> values = getConnection().getRegionServerWithRetries(callable);
> } catch (IOException e) {
> if (e instanceof UnknownScannerException &&
> lastNext + scannerTimeout < System.currentTimeMillis()) {
> ScannerTimeoutException ex = new ScannerTimeoutException();
> ex.initCause(e);
> throw ex;
> }
> throw e;
> }
> {code}
> Is there any reason why TIFB does not catch ScannerTimeoutException?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
