You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Sreenath Somarajapuram (JIRA)" <ji...@apache.org> on 2015/09/09 20:17:47 UTC

[jira] [Updated] (TEZ-2795) AM web service V2: Refactoring & optimization

     [ https://issues.apache.org/jira/browse/TEZ-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sreenath Somarajapuram updated TEZ-2795:
----------------------------------------
    Description: 
Make error handling better
- Currently on error the function returns null, and the callee checks for null value which is not the best approach.
- Guess the best is to modify the exception to give a meaning full message, and then re-throw the same. A base try..catch block can be put in to handle all exceptions.
- Gracefully fail invalid ids -  Server shouldn't return error even if ids are invalid.

  was:
Make error handling better
- Currently on error the function returns null, and the callee checks for null value which is not the best approach.
- Guess the best is to modify the exception to give a meaning full message, and then re-throw the same. A base try..catch block can be put in to handle all exceptions.


> AM web service V2: Refactoring & optimization
> ---------------------------------------------
>
>                 Key: TEZ-2795
>                 URL: https://issues.apache.org/jira/browse/TEZ-2795
>             Project: Apache Tez
>          Issue Type: Sub-task
>          Components: UI
>            Reporter: Sreenath Somarajapuram
>
> Make error handling better
> - Currently on error the function returns null, and the callee checks for null value which is not the best approach.
> - Guess the best is to modify the exception to give a meaning full message, and then re-throw the same. A base try..catch block can be put in to handle all exceptions.
> - Gracefully fail invalid ids -  Server shouldn't return error even if ids are invalid.



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