[
https://issues.apache.org/jira/browse/TAJO-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyunsik Choi updated TAJO-1625:
-------------------------------
Fix Version/s: (was: 0.12)
0.12.0
> Recap error propagation system in Tajo
> --------------------------------------
>
> Key: TAJO-1625
> URL: https://issues.apache.org/jira/browse/TAJO-1625
> Project: Tajo
> Issue Type: Improvement
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.12.0
>
>
> In the current implementation, our error propagation system is not
> consistent.
> The primary problem comes with RPC. RPC just throws exception with the error
> message. So it makes error handling and the failure tests very difficult.
> Another problem is that the exact error status is not conveyed to users.
> The solution is to refactor all exceptions used in Tajo to have error code
> number and stack trace throughout all codes and rpc responses.
> I'm surveying all error cases used in Tajo at
> https://cwiki.apache.org/confluence/display/TAJO/Error+Code. I would
> appreciate your effort If you help to this survey.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
