flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6105) Properly handle InterruptedException in HadoopInputFormatBase
Date Tue, 18 Jul 2017 02:23:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091003#comment-16091003
] 

Ted Yu commented on FLINK-6105:
-------------------------------

Using InterruptedIOException is common practice in handling InterruptedException.
You can see a lot of such usage in, e.g. hadoop and hbase.

> 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
>            Assignee: mingleizhang
>
> 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.4.14#64029)

Mime
View raw message