[ 
https://issues.apache.org/jira/browse/HDFS-16141?focusedWorklogId=637143&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-637143
 ]

ASF GitHub Bot logged work on HDFS-16141:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Aug/21 21:23
            Start Date: 11/Aug/21 21:23
    Worklog Time Spent: 10m 
      Work Description: prasad-acit commented on pull request #3232:
URL: https://github.com/apache/hadoop/pull/3232#issuecomment-897164436


   > testFileCreationNamenodeRestart
   
   I am not facing this issue with 3.1.1 branch. Some issue related restart 
scenario, let me take a look. I will update on this.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 637143)
    Time Spent: 1.5h  (was: 1h 20m)

> [FGL] Address permission related issues with File / Directory
> -------------------------------------------------------------
>
>                 Key: HDFS-16141
>                 URL: https://issues.apache.org/jira/browse/HDFS-16141
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Renukaprasad C
>            Assignee: Renukaprasad C
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Post FGL implementation (MKDIR & Create File), there are existing UTs got 
> impacted which needs to be addressed.
> Failed Tests:
> TestDFSPermission
> TestPermission
> TestFileCreation
> TestDFSMkdirs (Added tests)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to