You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/11/07 00:09:34 UTC

[jira] [Commented] (SQOOP-649) REST API : Stop using exceptions as a way to transfer regular error states between client and server

    [ https://issues.apache.org/jira/browse/SQOOP-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201161#comment-14201161 ] 

Veena Basavaraj commented on SQOOP-649:
---------------------------------------

+ 1

We need to use standard HTTP response codes

trying to update/ delete / get an unknown resource should be 400 I beleive


> REST API : Stop using exceptions as a way to transfer regular error states between client and server
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-649
>                 URL: https://issues.apache.org/jira/browse/SQOOP-649
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
>
>
> We're currently using exceptions as means of moving incorrect states between client and server. For example "Can't delete this job id as it already exists", ... I believe that we should encode such issues in more better way and use exceptions only for exceptional state.



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