[
https://issues.apache.org/jira/browse/HADOOP-18002?focusedWorklogId=680251&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-680251
]
ASF GitHub Bot logged work on HADOOP-18002:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Nov/21 12:14
Start Date: 11/Nov/21 12:14
Worklog Time Spent: 10m
Work Description: mukund-thakur commented on pull request #3641:
URL: https://github.com/apache/hadoop/pull/3641#issuecomment-966254315
Why can't we just revert the commit rather than deleting it? Also there is
delete idempotency checks as well not sure if they also use same LMT check.
--
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: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 680251)
Time Spent: 50m (was: 40m)
> abfs rename idempotency broken -remove recovery
> -----------------------------------------------
>
> Key: HADOOP-18002
> URL: https://issues.apache.org/jira/browse/HADOOP-18002
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 3.3.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
