From hadoop-dev-return-4761-apmail-lucene-hadoop-dev-archive=lucene.apache.org@lucene.apache.org Thu Nov 02 16:22:42 2006 Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 50421 invoked from network); 2 Nov 2006 16:22:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Nov 2006 16:22:41 -0000 Received: (qmail 75528 invoked by uid 500); 2 Nov 2006 16:22:51 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 75458 invoked by uid 500); 2 Nov 2006 16:22:51 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 75449 invoked by uid 99); 2 Nov 2006 16:22:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 08:22:51 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [207.126.228.149] (HELO rsmtp1.corp.yahoo.com) (207.126.228.149) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 08:22:35 -0800 Received: from [10.0.1.3] (snvvpn1-10-72-72-c211.corp.yahoo.com [10.72.72.211]) by rsmtp1.corp.yahoo.com (8.13.6/8.13.6/y.rout) with ESMTP id kA2GM7cX001318 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 2 Nov 2006 08:22:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:content-type:message-id: content-transfer-encoding:from:subject:date:to:x-mailer; b=2FDjtw5JhICTK0rVwGh+jQiIU1o4qTzmgMT5ZTAu9fLCBDwLDkgAsyTeqgJPivIK Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <15520386.1162451657672.JavaMail.root@brutus> References: <15520386.1162451657672.JavaMail.root@brutus> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <64659B1D-926B-4221-840D-D5368D7F32E5@yahoo-inc.com> Content-Transfer-Encoding: 7bit From: Nigel Daley Subject: Re: [jira] Commented: (HADOOP-667) Path configuration properties should not be comma separated Date: Thu, 2 Nov 2006 08:22:08 -0800 To: hadoop-dev@lucene.apache.org X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org The config files are XML. Seems like multiple name/value pairs should work. On Nov 1, 2006, at 11:14 PM, eric baldeschwieler (JIRA) wrote: > [ http://issues.apache.org/jira/browse/HADOOP-667? > page=comments#action_12446468 ] > > eric baldeschwieler commented on HADOOP-667: > -------------------------------------------- > > humm, so how do we specify a list of paths? > > sounds like a conversation about quoting conventions is needed > >> Path configuration properties should not be comma separated >> ----------------------------------------------------------- >> >> Key: HADOOP-667 >> URL: http://issues.apache.org/jira/browse/HADOOP-667 >> Project: Hadoop >> Issue Type: Bug >> Components: fs >> Affects Versions: 0.7.2 >> Reporter: Nigel Daley >> Priority: Minor >> >> A few configuration properties allow multiple directory paths >> separated by comma's (,). Since comma is a valid character for a >> directory name, it should not be used as a path separator. >> At a minimum, this applies to these properties: >> mapred.local.dir >> dfs.name.dir >> [ I also wonder how robust the implementation is against paths >> that contain spaces. ] > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the > administrators: http://issues.apache.org/jira/secure/ > Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/ > software/jira > >