hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14402) roll out StreamCapabilities across output streams of all filesystems
Date Mon, 21 Aug 2017 11:34:02 GMT

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

Steve Loughran commented on HADOOP-14402:

As oss://, s3a:// and swift don't do syncable, they're already sorted with the base "return
false". Adding the others in Hadoop-13327

> roll out StreamCapabilities across output streams of all filesystems
> --------------------------------------------------------------------
>                 Key: HADOOP-14402
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14402
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs, fs/adl, fs/azure, fs/oss, fs/s3, fs/swift
>    Affects Versions: 3.0.0-alpha4
>            Reporter: Steve Loughran
> HDFS-11644 added a way to probe streams for capabilities, with dfsoutput stream implementing
> We should roll this out to all our output streams, with capabilities to define
> * is metadata in sync with flushed data (HDFS: no)
> * does LocalFileSystem really do a sync/flush (as I don't think any subclass of ChecksumFS
does, so {{FSOutputSummer}} should declare this in its capabilities
> * are intermediate writes visible *at all*? 
> * Is close() potentially a long operation (for object stores, yes, on a case-by-case
> We'll need useful names for these options, obviously, tests, etc etc

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