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

ASF GitHub Bot logged work on HADOOP-17396:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Nov/20 10:11
            Start Date: 26/Nov/20 10:11
    Worklog Time Spent: 10m 
      Work Description: steveloughran merged pull request #2491:
URL: https://github.com/apache/hadoop/pull/2491


   


----------------------------------------------------------------
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:
[email protected]


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

    Worklog Id:     (was: 516971)
    Time Spent: 50m  (was: 40m)

> ABFS: testRenameFileOverExistingFile Fails after Contract test update
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-17396
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17396
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.3.0
>            Reporter: Sneha Vijayarajan
>            Assignee: Sneha Vijayarajan
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Post updates to rename on existing file test, ABFS contract test is having 
> failure.
> Updates were made in the AbstractContractTest class in 
> https://issues.apache.org/jira/browse/HADOOP-17365.
> To align to test expectation, ABFS tests need config 
> "fs.contract.rename-returns-false-if-dest-exists" set to true. 
>  



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