[
https://issues.apache.org/jira/browse/HADOOP-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-13631:
-----------------------------------
Hadoop Flags: Reviewed
+1, assuming [~eddyxu] thinks his feedback has been resolved satisfactorily.
I think this {{move}} interface does make sense based on our current goals with
metadata backed by DynamoDB. Eddy has a good point that some implementations
might operate better by working with the source and destination path, like the
existing interface. I could imagine an implementation backed by a simplified
NameNode or maybe NFS (though I'm generally wary of NFS high availability
capabilities). When that comes up, maybe the interface could evolve to include
both the collections and the source and destination path, and the
implementation can decide which parameters to use.
I think we'll have freedom to evolve the {{MetadataStore}} interface. We're
not planning to make it public with strict backward compatibility guarantees,
so we can change it easily later.
> S3Guard: implement move() for LocalMetadataStore, add unit tests
> ----------------------------------------------------------------
>
> Key: HADOOP-13631
> URL: https://issues.apache.org/jira/browse/HADOOP-13631
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Aaron Fabbri
> Assignee: Aaron Fabbri
> Attachments: HADOOP-13631-HADOOP-13345.001.patch
>
>
> Building on HADOOP-13573 and HADOOP-13452, implement move() in
> LocalMetadataStore and associated MetadataStore unit tests.
> (Making this a separate JIRA to break up work into decent-sized and
> reviewable chunks.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
