Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B2A281055F for ; Fri, 6 Sep 2013 02:21:39 +0000 (UTC) Received: (qmail 49386 invoked by uid 500); 6 Sep 2013 02:21:34 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 49295 invoked by uid 500); 6 Sep 2013 02:21:34 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 49288 invoked by uid 99); 6 Sep 2013 02:21:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Sep 2013 02:21:34 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Sep 2013 02:21:30 +0000 Received: by mail-ie0-f170.google.com with SMTP id 16so4716183iea.15 for ; Thu, 05 Sep 2013 19:21:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=8AUO5dJkZOW/20enVeAweMf6DZ0SyFGVzMBsCH14698=; b=XZt9wLbL9iAX1cMpQy4fwqCyC8c2FMufLMMnJuyPCWjr2eRhlkMEedjEo0rNmABs1u f2TGuxkgC8xMQ1KCU0PR7VfSseUP6vD2mygKAFl0oZBFfPs9m9N02iHZsAH9rMem1lfF JO7h1HtK/aS9GFl2yYIu92BkqYCgwPbwHnYKC2PAx4SfD0FsJ/t1kqP2IXzWl1jtlrJX csC9+O/4jaNlvqIxZlnNbv31gY4v9pheh10Xln8BfK0zi7jUWcc8F1t+wj8hsR84xcQk s9zCbTzJJBfTPriFfFuoFtz9HCbGGnfjwl3LEYQ8L8MZGerEGvrVtoKbBrlSjtlTddVs KQ4Q== X-Gm-Message-State: ALoCoQkWUzcg3R8Av8zbILK8A3I/JV4xhYQfxF/dz1jLgd1o6CgwXVqt2+GNA0V6Lgi+/RQGFoiO X-Received: by 10.50.178.167 with SMTP id cz7mr8207374igc.7.1378434069913; Thu, 05 Sep 2013 19:21:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.56.105 with HTTP; Thu, 5 Sep 2013 19:20:48 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Fri, 6 Sep 2013 07:50:48 +0530 Message-ID: Subject: Re: How to support the (HDFS) FileSystem API of various Hadoop Distributions? To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hello, There are a few additions to the FileSystem that may bite you across versions, but if you pick an old stable version such as Apache Hadoop 0.20.2, and stick to only its offered APIs, it would work better across different version dependencies as we try to maintain FileSystem as a stable interface as much as we can (there was also more recent work to ensure the stabilization). I looked over your current code state and it seemed to have pretty stable calls that I think have existed across several versions and exists today, but I did notice you had to remove an isRoot as part of a previous commit, which may have lead to this question? If that doesn't work for you, you can also switch out to using sub-modules carrying code specific to a build version type (such as what HBase does at https://github.com/apache/hbase/tree/trunk/ (see the hbase-hadoop-compat directories)). On Fri, Sep 6, 2013 at 2:59 AM, Christian Schneider wrote: > Hi, > I start to write a small ncdu clone to browse HDFS on the CLI > (http://nchadoop.org/). Currently i'm testing it against CDH4, - but I like > to make it available for a wider group of users (Hortonworks, ..). > > Is it enough to pick different vanilla Versions (for IPC 5, 7)? > > Best Regards, > Christian. > -- Harsh J