[
https://issues.apache.org/jira/browse/TAJO-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702591#comment-14702591
]
ASF GitHub Bot commented on TAJO-1758:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/700
TAJO-1758: Some TajoRuntimeException should be restored as TajoException.
…ion in client side.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1758
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/700.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #700
----
commit 75a92ce44a841d04e3bcd7d09cb27ad83a13c5e2
Author: Hyunsik Choi <[email protected]>
Date: 2015-08-19T06:43:14Z
TAJO-1758: Some TajoRuntimeException should be restored as TajoException in
client side.
----
> 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)
