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 247EA200D37 for ; Wed, 25 Oct 2017 21:03:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 22FA01609CE; Wed, 25 Oct 2017 19:03:07 +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 6FAA5160BDA for ; Wed, 25 Oct 2017 21:03:06 +0200 (CEST) Received: (qmail 86328 invoked by uid 500); 25 Oct 2017 19:03: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 86258 invoked by uid 99); 25 Oct 2017 19:03:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Oct 2017 19:03:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CED4D180805 for ; Wed, 25 Oct 2017 19:03:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vYj-f_EBMLZF for ; Wed, 25 Oct 2017 19:03:04 +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 DD5B05FE64 for ; Wed, 25 Oct 2017 19:03: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 D9BABE0F4E for ; Wed, 25 Oct 2017 19:03: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 56969212FF for ; Wed, 25 Oct 2017 19:03:01 +0000 (UTC) Date: Wed, 25 Oct 2017 19:03:01 +0000 (UTC) From: "Manoj Govindassamy (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-14136) Default FS For ViewFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 25 Oct 2017 19:03:07 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Govindassamy resolved HADOOP-14136. ----------------------------------------- Resolution: Duplicate Fix Version/s: 3.0.0 Target Version/s: 3.0.0 [~xkrogen], Yes, this is taken care as part of HADOOP-13055. Closing this as a DUP. Thanks. > Default FS For ViewFS > --------------------- > > Key: HADOOP-14136 > URL: https://issues.apache.org/jira/browse/HADOOP-14136 > Project: Hadoop Common > Issue Type: New Feature > Components: fs, viewfs > Reporter: Erik Krogen > Assignee: Manoj Govindassamy > Fix For: 3.0.0 > > > It would be useful if ViewFS had the ability to designate one FileSystem as a "primary"/"default" to fall back to in the case that an entry in the mount table is not found. Consider the situation when you have a mount table that looks like: > {code} > /data -> hdfs://nn1/data > /logs -> hdfs://nn1/logs > /user -> hdfs://nn1/user > /remote -> hdfs://nn2/remote > {code} > {{nn1}} here is being used as the primary, with a specific directory 'remote' being offloaded to another namenode. This works, but if we want to add another top-level directory to {{nn1}}, we have to update all of our client-side mount tables. Merge links (HADOOP-8298) could be used to achieve this but they do not seem to be coming soon; this special case of a default FS is much simpler - try to resolve through the VFS mount table, if not found, then resolve to the defaultFS. > There is a good discussion of this at https://issues.apache.org/jira/browse/HADOOP-13055?focusedCommentId=15733822&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15733822 -- 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