You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2021/02/10 14:59:01 UTC
[jira] [Resolved] (HADOOP-14402) roll out StreamCapabilities across
output streams of all filesystems
[ https://issues.apache.org/jira/browse/HADOOP-14402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-14402.
-------------------------------------
Fix Version/s: 3.3.1
Resolution: Fixed
> 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
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.3.1
>
>
> HDFS-11644 added a way to probe streams for capabilities, with dfsoutput stream implementing some.
> 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 basis)
> We'll need useful names for these options, obviously, tests, etc etc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org