[
https://issues.apache.org/jira/browse/FLINK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112030#comment-16112030
]
ASF GitHub Bot commented on FLINK-6105:
---------------------------------------
Github user zhangminglei commented on the issue:
https://github.com/apache/flink/pull/4316
@greghogan I saw Ted comment on the jira before. But I am not sure whether
we will adopt Ted's comments. So, that is why I leave this PR until someone
adopt it, I will keep working on this then. As refers to what you said logging
a different exception, hmm, probably. I would think it will give us more clear
exception. @tedyu What do you think of this ?
> 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)
