hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Fabbri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13651) S3Guard: S3AFileSystem Integration with MetadataStore
Date Fri, 04 Nov 2016 05:10:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635275#comment-15635275

Aaron Fabbri commented on HADOOP-13651:

I will address above pre-commit issues after I get the feature branch rebased on trunk.

[~stevel@apache.org], when feature branches get merged to trunk, is it as a fast-forward,
or as a merge commit?

Many of the commits on this feature branch need reworking for trunk s3a changes, and I'm wondering
if I should go through the history one by one, rewriting those commits to work against trunk
(e.g. S3AFileStatus constructor args changed), or just add a Fixup commit on top of the feature
branch to get it to compile on trunk's S3A code.)

> S3Guard: S3AFileSystem Integration with MetadataStore
> -----------------------------------------------------
>                 Key: HADOOP-13651
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13651
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Aaron Fabbri
>            Assignee: Aaron Fabbri
>         Attachments: HADOOP-13651-HADOOP-13345.001.patch, HADOOP-13651-HADOOP-13345.002.patch,
HADOOP-13651-HADOOP-13345.003.patch, HADOOP-13651-HADOOP-13345.004.patch
> Modify S3AFileSystem et al. to optionally use a MetadataStore for metadata consistency
and caching.
> Implementation should have minimal overhead when no MetadataStore is configured.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message