You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2014/08/17 19:56:18 UTC

[jira] [Updated] (TEZ-1444) Wrap interrupted in a specific Exception

     [ https://issues.apache.org/jira/browse/TEZ-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Seth updated TEZ-1444:
--------------------------------

    Description: 
TEZ-1331 changed some APIs to throw InterruptedException in an IOException wrapper.
It's useful to be able to determine whether the exception thrown was "interrupted" or not, since there's a good chance the interrupt was caused by user code itself, in which case Interrupts can be caught and ignored by the user code which likely issued the interrupt.

  was:
TEZ-1331 changed some APIs to throw InterruptedException in an IOException wrapper.
It's useful to be able to determine whether the exception thrown was "interrupted" or not, since there's a good chance the interrupt was caused by user code itself, in which case Interrupts can be caught and ignored.


> Wrap interrupted in a specific Exception
> ----------------------------------------
>
>                 Key: TEZ-1444
>                 URL: https://issues.apache.org/jira/browse/TEZ-1444
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Priority: Blocker
>
> TEZ-1331 changed some APIs to throw InterruptedException in an IOException wrapper.
> It's useful to be able to determine whether the exception thrown was "interrupted" or not, since there's a good chance the interrupt was caused by user code itself, in which case Interrupts can be caught and ignored by the user code which likely issued the interrupt.



--
This message was sent by Atlassian JIRA
(v6.2#6252)