[
https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636030#comment-16636030
]
Da Zhou edited comment on HADOOP-15812 at 10/2/18 7:55 PM:
-----------------------------------------------------------
Reorder the msg displayed in the first line.
Previously the first line of error msg only contains :
\{HTTP_METHOD} \{REQUEST_URL},
as a result, a failed "ls" hadoop cmd will have a error msg like this :
{noformat}
ls: HEAD https://XXXX
{noformat}
I did a minor change to include the HTTP status code in the first line, so that
user can know the possible reason why it failed. If user need more information,
they need to go the log file and check.
I didn't include the other information : "statusDescription",
"storageErrorcode" and "storageErrorMessage" because that would make the msg
too long for one line, the other reason is that for HEAD request, the response
doesn't contain payload, so "statusDescription" and "storageErrorcode" will be
null in that case, which might make the msg confusing for user. So I think HTTP
status code should be good enough.
After the change the failed cmd error msg become :
{noformat}
ls: HEAD StatusCode=403 http://XXX
{noformat}
Tests passed:.
Namespace not enabled account, using shared Key
Tests run: 36, Failures: 0, Errors: 0, Skipped: 0
Tests run: 306, Failures: 0, Errors: 0, Skipped: 198
Tests run: 165, Failures: 0, Errors: 0, Skipped: 15
Namespace enabled account, using Oauth
Tests run: 36, Failures: 0, Errors: 0, Skipped: 0
Tests run: 306, Failures: 0, Errors: 0, Skipped: 35
Tests run: 165, Failures: 0, Errors: 0, Skipped: 21
was (Author: danielzhou):
Reorder the msg displayed in the first line.
Previously the fist line of error msg only contains :
\{HTTP_METHOD\} \{REQUEST_URL\},
as a result, a failed "ls" hadoop cmd will have a error msg like this :
{noformat}
ls: HEAD https://XXXX
{noformat}
I did a minor change to include the HTTP status code in the first line, so that
user can know the possible reason why it failed. If user need more information,
they need to go the log file and check.
I didn't include the other information : "statusDescription",
"storageErrorcode" and "storageErrorMessage" since that would make the msg too
long for one line, and HTTP status code should be good enough.
So after the change the failed cmd error msg is :
{noformat}
ls: HEAD StatusCode=403 http://XXX
{noformat}
Tests passed:.
Namespace not enabled account, using shared Key
Tests run: 36, Failures: 0, Errors: 0, Skipped: 0
Tests run: 306, Failures: 0, Errors: 0, Skipped: 198
Tests run: 165, Failures: 0, Errors: 0, Skipped: 15
Namespace enabled account, using Oauth
Tests run: 36, Failures: 0, Errors: 0, Skipped: 0
Tests run: 306, Failures: 0, Errors: 0, Skipped: 35
Tests run: 165, Failures: 0, Errors: 0, Skipped: 21
> ABFS: Improve AbfsRestOperationException format to ensure full msg can be
> displayed on console
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-15812
> URL: https://issues.apache.org/jira/browse/HADOOP-15812
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.0
> Reporter: Da Zhou
> Assignee: Da Zhou
> Priority: Major
> Attachments: HADOOP-15812-001.patch
>
>
> AbfsRestOperationException msg contains multiple "\n" for displaying nicely,
> however, hadoop cmd class split the error msg by "\n" and display the first
> string in console, which lead to the incomplete error msg shown in console.
> Hence we need to improve this format.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
