[
https://issues.apache.org/jira/browse/ATLAS-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-1200:
-------------------------------
Description:
Currently the error/exception messages are hand constructed all over the Atlas
code base, making it hard to understand the origin of the problem. Also since
Atlas is moving towards a more RESTful nature it's better to create a catalog
for the error message with support for localization
Proposal:
Format:
internal_error_code=external_error_code|error_description
internal_error_code_status=http_status_code
e.g.
entity_not_found=entity_not_found|Given entity doesn't exist
entity_not_found_status=404
was:
Currently the error/exception messages are hand constructed all over the Atlas
code base, making it hard to understand the origin of the problem. Also since
Atlas is moving towards a more RESTful nature it's better to create a catalog
for the error message with support for localization
Proposal:
Format: internal_error_code=http_status_code|error_description
e.g.
entity_not_found=404|Given entity doesn't exist
> Enhance the Exception mechanism
> -------------------------------
>
> Key: ATLAS-1200
> URL: https://issues.apache.org/jira/browse/ATLAS-1200
> Project: Atlas
> Issue Type: Improvement
> Affects Versions: 0.7-incubating, 0.8-incubating
> Reporter: Apoorv Naik
> Assignee: Apoorv Naik
>
> Currently the error/exception messages are hand constructed all over the
> Atlas code base, making it hard to understand the origin of the problem. Also
> since Atlas is moving towards a more RESTful nature it's better to create a
> catalog for the error message with support for localization
> Proposal:
> Format:
> internal_error_code=external_error_code|error_description
> internal_error_code_status=http_status_code
> e.g.
> entity_not_found=entity_not_found|Given entity doesn't exist
> entity_not_found_status=404
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
