[
https://issues.apache.org/jira/browse/TAJO-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632682#comment-14632682
]
ASF GitHub Bot commented on TAJO-1670:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/621#issuecomment-122618809
@hyunsik thank you for the nice work.
In addition to the above my comments, I have more comments to discuss with
you.
* Duplicate exception VS Ambiguous exception
* It seems that every exception is the duplicate exception when there
already exists the same thing. However, IMHO, it would be better if we support
ambiguous exception as well depending on the situation. For example, the
duplicate exception is appropriate for creating a table while the ambiguous
exception is appropriate for getting or dropping a table.
* CatalogExceptionUtil and ExceptionUtil
* These classes look good, but only some methods are used in your
implementation. Do you have any reason?
* In your implementation, ```INSUFFICIENT_PRIVILEGE``` is threw if uses try
to remove the default database. I think that it would be much proper to use
this error code for the real privilege violation after we support the privilege
feature. I've also tested that pgsql allows for users to remove the default
database if they have sufficient privilege. I wonder why you chose this
implementation.
Additionally, please add a description of ```TajoInternalError``` on our
wiki.
> Refactor client errors and exceptions
> -------------------------------------
>
> Key: TAJO-1670
> URL: https://issues.apache.org/jira/browse/TAJO-1670
> Project: Tajo
> Issue Type: Sub-task
> Components: Java Client, TajoMaster, Worker
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.11.0
>
>
> The main objective is to refactor the error and exception system in client
> side and its connected parts like TajoMaster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
