[ https://issues.apache.org/jira/browse/HADOOP-14041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866447#comment-15866447 ]
Sean Mackrory commented on HADOOP-14041: ---------------------------------------- I missed the javadoc issue locally. The hadoop-common failures are not related. The hadoop-aws failure is something I've seen a lot locally and have mentioned elsewhere but it seems no one else was seeing it and occasionally I don't see it (no idea how - we use FileStatus all over S3Guard). Removing the assertion and not casting to S3AFileStatus in that function makes everything work nicely. Has no one else seen this failure? I'll upload a new patch that addresses the javadoc oversight. > CLI command to prune old metadata > --------------------------------- > > Key: HADOOP-14041 > URL: https://issues.apache.org/jira/browse/HADOOP-14041 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Reporter: Sean Mackrory > Assignee: Sean Mackrory > Attachments: HADOOP-14041-HADOOP-13345.001.patch, > HADOOP-14041-HADOOP-13345.002.patch, HADOOP-14041-HADOOP-13345.003.patch, > HADOOP-14041-HADOOP-13345.004.patch > > > Add a CLI command that allows users to specify an age at which to prune > metadata that hasn't been modified for an extended period of time. Since the > primary use-case targeted at the moment is list consistency, it would make > sense (especially when authoritative=false) to prune metadata that is > expected to have become consistent a long time ago. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org