[GitHub] [hadoop-ozone] elek commented on pull request #1110: HDDS-3843. Throw the specific exception other than NPE.

2020-08-24 Thread GitBox


elek commented on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-679204042


   /pending @maobaolong Do we have the same error with this patch as AWS?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org



[GitHub] [hadoop-ozone] elek commented on pull request #1110: HDDS-3843. Throw the specific exception other than NPE.

2020-06-30 Thread GitBox


elek commented on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-651683723


   > So, you mean, we should keep s3g's behavior consistent with aws s3?
   
   Yes, I think we should follow the behavior of AWS. There are so many s3 
tools: doing exactly the same will cause less problem.
   
   But I agree that NPE should be replaced with more meaningful errors.  
   
   @maobaolong Do we have the same error with this patch as AWS?
   
   (@bharatviswa504 thanks the screenshot. I didn't know that postman can 
generate the aws signaure header. Very useful information, started to use 
postman again...)



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org