[
https://issues.apache.org/jira/browse/HDDS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDDS-560:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
+1
I agree with [~anu] that we need to clean up the exception handling for the
OzoneClient. It's very bad that we need to check the exception message to
identify NOT_FOUND problems.
Still I am not convinced that we need a checked exception, but as I wrote it's
more like a personal taste.
I just committed this to trunk. (We can do further improvements when we need.
For example when we will have more specific OzoneClient exceptions)
Thank you [~bharatviswa] the contribution.
> Create Generic exception class to be used by S3 rest services
> -------------------------------------------------------------
>
> Key: HDDS-560
> URL: https://issues.apache.org/jira/browse/HDDS-560
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Attachments: HDDS-560.00.patch, HDDS-560.01.patch
>
>
> Exception class should have the following fields, and structure should be as
> below:
>
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <Error>
> <Code>NoSuchKey</Code>
> <Message>The resource you requested does not exist</Message>
> <Resource>/mybucket/myfoto.jpg</Resource>
> <RequestId>4442587FB7D0A2F9</RequestId>
> </Error>
> {code}
>
>
> https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
