Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11.0
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              hyunsik Hyunsik Choi
              Reporter:
              hyunsik Hyunsik Choi
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development