[
https://issues.apache.org/jira/browse/HDFS-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187634#comment-15187634
]
James Clampffer commented on HDFS-9792:
---------------------------------------
Just looked at this again, disregard my last comment. For some reason I
thought the C API could end up with two different permission denied error
strings.
+1
> libhdfs++: EACCES not setting errno correctly
> ---------------------------------------------
>
> Key: HDFS-9792
> URL: https://issues.apache.org/jira/browse/HDFS-9792
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Bob Hansen
> Assignee: Bob Hansen
> Attachments: HDFS-9792.HDFS-8707.000.patch,
> HDFS-9792.HDFS-8707.000.patch
>
>
> When libhdfs++ gets a permissions error, it is failing to initialize errnum.
> Due to changes passing in the night, the code in hdfs.cc that reads
> {code}
> case Status::Code::kPermissionDenied:
> if (!stat.ToString().empty())
> ReportError(EACCES, stat.ToString().c_str());
> else
> ReportError(EACCES, "Permission denied");
> break;
> {code}
> should read
> {code}
> case Status::Code::kPermissionDenied:
> errnum = EACCES;
> default_message = "Permission denied";
> break;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
