[HADOOP-18002] abfs rename idempotency broken -remove recovery

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.2
• Fix Version/s: 3.3.2
• Component/s: fs/azure
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 10/Nov/21 15:09
• Updated: 21/Jan/24 04:32
• Resolved: 16/Nov/21 11:18

Description

rename idempotency logic of HADOOP-17105 is broken as modtimes aren't uodated on rename.

remove, with the changes from the PR of HADOOP-17981.
also fix delete recovery test after HADOOP-17934

Issue Links

• contains: HADOOP-17989 ITestAzureBlobFileSystemDelete failing "Operations has null HTTP response"
• is related to: HADOOP-18012 ABFS: Enable config controlled ETag check for Rename idempotency
• is related to: HADOOP-17979 Interface EtagSource to allow FileStatus subclasses to provide etags
• relates to: HADOOP-17934 NullPointerException when no HTTP response set on AbfsRestOperation
• relates to: HADOOP-17981 Support etag-assisted renames in FileOutputCommitter
• links to: GitHub Pull Request #3641