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

Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2015/08/19 16:16:46 UTC

[jira] [Resolved] (TAJO-1758) Some TajoRuntimeException should be restored as TajoException in client side

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

Hyunsik Choi resolved TAJO-1758.
--------------------------------
    Resolution: Fixed

committed. Thank you for the quick review.

> Some TajoRuntimeException should be restored as TajoException in client side
> ----------------------------------------------------------------------------
>
>                 Key: TAJO-1758
>                 URL: https://issues.apache.org/jira/browse/TAJO-1758
>             Project: Tajo
>          Issue Type: Sub-task
>          Components: Java Client
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Minor
>             Fix For: 0.11.0, 0.12.0
>
>
> Some exceptions like NotImplementedException and UnsupportedException can occur in any methods. So, they are subclasses of TajoRuntimeException. But, it is hard for Client applications to handle TajoRuntimeException in the same way like TajoException. So, the final exception thrown from Client APIs must be TajoException. 
> The main purpose of this issue solves this problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)