[ 
https://issues.apache.org/jira/browse/HADOOP-19599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032963#comment-18032963
 ] 

ASF GitHub Bot commented on HADOOP-19599:
-----------------------------------------

github-actions[bot] commented on PR #7767:
URL: https://github.com/apache/hadoop/pull/7767#issuecomment-3447890882

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Fix file permission errors as per the platform
> ----------------------------------------------
>
>                 Key: HADOOP-19599
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19599
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: hadoop-common
>    Affects Versions: 3.5.0
>         Environment: Windows 10
>            Reporter: Gautham Banasandra
>            Assignee: Gautham Banasandra
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.0
>
>
> The file permission denial error message in Linux systems end with 
> "(Permission denied)" particularly.
> However, an error message in the same scenario on Windows ends with "(Access 
> is denied)" error.
> This results in a bug in 
> *org.apache.hadoop.fs.ChecksumFileSystem.ChecksumFSInputChecker* and also 
> leads to a unit test failure 
> *org.apache.hadoop.fs.TestFsShellCopy#testPutSrcFileNoPerm*.
> Thus, we need to make the appropriate check in accordance with the platform.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to