[
https://issues.apache.org/jira/browse/HADOOP-15038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784320#comment-16784320
]
Steve Loughran commented on HADOOP-15038:
-----------------------------------------
Keep an eye on HADOOP-15619
in particular, the bit where I don't think it's experimental HADOOP-14936
now, before that, if you had an uncommitted branch of the OSS connector which
imported the metastore stuff from hadoop-aws just to test, would that work?
Because that would help catch regression tests &c with that work as it goes on.
(Now that Alibaba is opening up DCs in EU, I should get an account. And with
the purchase of the Flink Dev team in berlin, recruit some more testers for
this code)
> Abstract MetadataStore in S3Guard into a common module.
> -------------------------------------------------------
>
> Key: HADOOP-15038
> URL: https://issues.apache.org/jira/browse/HADOOP-15038
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs
> Affects Versions: 3.2.0, 2.9.2, 3.0.3, 3.1.2
> Reporter: Genmao Yu
> Assignee: wujinhu
> Priority: Major
> Attachments: HADOOP-15038.001.patch
>
>
> Open this JIRA to discuss if we should move {{MetadataStore}} in {{S3Guard}}
> into a common module.
> Based on this work, other filesystem or object store can implement their own
> metastore for optimization (known issues like consistency problem and
> metadata operation performance). [[email protected]] and other guys have
> done many base and great works in {{S3Guard}}. It is very helpful to start
> work. I did some perf test in HADOOP-14098, and started related work for
> Aliyun OSS. Indeed there are still works to do for {{S3Guard}}, like
> metadata cache inconsistent with S3 and so on. It also will be a problem for
> other object store. However, we can do these works in parallel.
> [[email protected]] [~fabbri] [~drankye] Any suggestion is appreciated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
