[
https://issues.apache.org/jira/browse/HADOOP-14041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HADOOP-14041:
-----------------------------------
Attachment: HADOOP-14041-HADOOP-13345.002.patch
Attaching a patch that has added documentation, and better handling of
directories. The behavior is that if a directory's contents gets pruned and is
now empty, we will also prune that directory (and so on, for its parents, as
long as they're empty). Added tests to cover those considerations. Tested
against us-east-1.
Not sure if I've mentioned these already, but I'm seeing failures in the tests
of the table versioning. Pretty certain it's not related, so just calling it
out. I'll file a JIRA about it.
{code}
TestDynamoDBMetadataStore.testTableVersionMismatch:382->verifyTableInitialized:487
» ResourceNotFound
TestDynamoDBMetadataStore.testTableVersionRequired:367->verifyTableInitialized:487
» ResourceNotFound
{code}
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
