Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D54F7200CEC for ; Mon, 21 Aug 2017 13:45:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D46FA163B06; Mon, 21 Aug 2017 11:45:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2845B163B07 for ; Mon, 21 Aug 2017 13:45:06 +0200 (CEST) Received: (qmail 93744 invoked by uid 500); 21 Aug 2017 11:45:05 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 93675 invoked by uid 99); 21 Aug 2017 11:45:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2017 11:45:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8B334C247F for ; Mon, 21 Aug 2017 11:45:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id OzSRdnACJwXH for ; Mon, 21 Aug 2017 11:45:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6E6815FE5F for ; Mon, 21 Aug 2017 11:45:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6D1FBE0D5B for ; Mon, 21 Aug 2017 11:45:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E113325389 for ; Mon, 21 Aug 2017 11:45:00 +0000 (UTC) Date: Mon, 21 Aug 2017 11:45:00 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14402) roll out StreamCapabilities across output streams of all filesystems MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 21 Aug 2017 11:45:07 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135064#comment-16135064 ] Steve Loughran commented on HADOOP-14402: ----------------------------------------- +I'm not doing anything about declaring new capabilities, not here > 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 > > 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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org