Return-Path: Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: (qmail 59012 invoked from network); 23 Mar 2010 10:22:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Mar 2010 10:22:33 -0000 Received: (qmail 98346 invoked by uid 500); 23 Mar 2010 10:22:33 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 98112 invoked by uid 500); 23 Mar 2010 10:22:30 -0000 Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-user@hadoop.apache.org Delivered-To: mailing list hdfs-user@hadoop.apache.org Received: (qmail 98104 invoked by uid 99); 23 Mar 2010 10:22:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 10:22:29 +0000 X-ASF-Spam-Status: No, hits=0.9 required=10.0 tests=AWL,FREEMAIL_FROM,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of zjffdu@gmail.com designates 209.85.212.48 as permitted sender) Received: from [209.85.212.48] (HELO mail-vw0-f48.google.com) (209.85.212.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 10:22:21 +0000 Received: by vws14 with SMTP id 14so1151121vws.35 for ; Tue, 23 Mar 2010 03:22:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=7kBa+EVzfFtjX8C2SSeQkKbF5sfkETuzdF0VA7E9B8M=; b=ezpg8PpvSK8m8pfxWo9osRVlRN+/REgogICK3fFhWOWLY5iF5ewqSvtbvaBNraD15L 3IuF1N4WSRL8TP92jOFW1+PZfTPjG1yDEB+n2tYQMYHzE+mHjJ8gVn1+ebsopCRr05OA GkQPlrZFGI8VKIN5cd12POweObNzYpTwe60fE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jwg7TCwF/Lnbb6SvCDbJgVPjqh0DGN94WTF32uK9URKry1RsCvmjU7HannjW9qtluM NxrOhnwHsK6a/OHuLhFT8rX2ub9WwzHvylJWPNRVuuJv7TPy3QueoFjxdGrTotE2lFXi xeVeNG+YVk0D4/Lqa1sMDqf/oyA3euuH6RUV4= MIME-Version: 1.0 Received: by 10.220.107.8 with SMTP id z8mr3581648vco.74.1269339720627; Tue, 23 Mar 2010 03:22:00 -0700 (PDT) Date: Tue, 23 Mar 2010 18:22:00 +0800 Message-ID: <8211a1321003230322n4c3a911bp651555482a35abfd@mail.gmail.com> Subject: This format path "{2009/12,2010/01}" is not supported in FileSystem.globStatus From: Jeff Zhang To: hdfs-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=00c09f905b0425b80b0482752f2f --00c09f905b0425b80b0482752f2f Content-Type: text/plain; charset=UTF-8 Hi all, As my title shows, it seems that "{2009/12,2010/01}" is not supported in FileSystem.globStatus, but in my opinion, it would be better if hdfs can support this kind of path. Does hadoop has any other way to achieve this or has any plan to implement this ? -- Best Regards Jeff Zhang --00c09f905b0425b80b0482752f2f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

As my title shows, it seems that "{20= 09/12,2010/01}" is not supported in FileSystem.globStatus, but in my o= pinion, it would be better if hdfs can support this kind of path. Does hado= op has any other way to achieve this or has any plan to implement this ?

--
Best Regards

Jeff Zhang
--00c09f905b0425b80b0482752f2f--