[ https://issues.apache.org/jira/browse/HADOOP-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16195441#comment-16195441 ]
Aaron Fabbri commented on HADOOP-13974: --------------------------------------- Thanks [~ste...@apache.org]. I was thinking something similar. I'm using the same args for {{-list}} and {{-abort}} so you can specify age with both and see what you are going to delete with {{-list}} before you do {{-abort}}. On the {{<age string>}} part, there is already a way of specifying age for the {{s3guard prune}} command. It basically has four possible options {{-days, -hours, -minutes, -seconds}} was going to use that for consistency. Sound ok? I have multipart upload listing iterators (factored out of S3AFileSystem as much as possible) with integration tests, and am finishing up the CLI tool and integration tests. Should have a v1 patch to post soon. > S3a CLI to support list/purge of pending multipart commits > ---------------------------------------------------------- > > Key: HADOOP-13974 > URL: https://issues.apache.org/jira/browse/HADOOP-13974 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.0.0-beta1 > Reporter: Steve Loughran > Assignee: Aaron Fabbri > > The S3A CLI will need to be able to list and delete pending multipart > commits. > We can do the cleanup already via fs.s3a properties. The CLI will let scripts > stat for outstanding data (have a different exit code) and permit batch jobs > to explicitly trigger cleanups. > This will become critical with the multipart committer, as there's a > significantly higher likelihood of commits remaining outstanding. > We may also want to be able to enumerate/cancel all pending commits in the FS > tree -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org