[ https://issues.apache.org/jira/browse/FLINK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated FLINK-6105: -------------------------- Description: When catching InterruptedException, we should throw InterruptedIOException instead of IOException. The following example is from HadoopInputFormatBase : {code} try { splits = this.mapreduceInputFormat.getSplits(jobContext); } catch (InterruptedException e) { throw new IOException("Could not get Splits.", e); } {code} There may be other places where IOE is thrown. was: When catching InterruptedException, we should throw InterruptedIOException instead of IOException. The following example is from HadoopInputFormatBase : {code} try { splits = this.mapreduceInputFormat.getSplits(jobContext); } catch (InterruptedException e) { throw new IOException("Could not get Splits.", e); } {code} There may be other places where IOE is thrown. > Properly handle InterruptedException in HadoopInputFormatBase > ------------------------------------------------------------- > > Key: FLINK-6105 > URL: https://issues.apache.org/jira/browse/FLINK-6105 > Project: Flink > Issue Type: Bug > Components: DataStream API > Reporter: Ted Yu > > When catching InterruptedException, we should throw InterruptedIOException > instead of IOException. > The following example is from HadoopInputFormatBase : > {code} > try { > splits = this.mapreduceInputFormat.getSplits(jobContext); > } catch (InterruptedException e) { > throw new IOException("Could not get Splits.", e); > } > {code} > There may be other places where IOE is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)