[
https://issues.apache.org/jira/browse/HDFS-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674065#comment-13674065
]
Suresh Srinivas commented on HDFS-4872:
---------------------------------------
bq. Add modTime parameter to delete operation with the meaning that the object
is deleted only if its modification time is <= than modTime parameter.
How is time synchronization between client and server done?
Another approach, use inode id to delete a file. But this has the disadvantage
of client having to know the inode id before issuing delete.
> Idempotent delete operation.
> ----------------------------
>
> Key: HDFS-4872
> URL: https://issues.apache.org/jira/browse/HDFS-4872
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.0.4-alpha
> Reporter: Konstantin Shvachko
>
> Making delete idempotent is important to provide uninterrupted job execution
> in case of HA failover.
> This is to discuss different approaches to idempotent implementation of
> delete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
