Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1556983147.149241268117367416.JavaMail.jira@brutus.apache.org>
Date: Tue, 9 Mar 2010 06:49:27 +0000 (UTC)
From: "Rodrigo Schmidt (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1579) archive: check and possibly
 replace the space charater in paths
In-Reply-To: <1568659007.148471268115327851.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842938#action_12842938 ] 

Rodrigo Schmidt commented on MAPREDUCE-1579:
--------------------------------------------

I agree, but I really think MAPREDUCE-1578 should be solved first. The way it is now, if we ever change the protocol on HarFileSystem, HadoopArchives will start generating old files with new version numbers, which is much more dangerous in my opinion.

> archive: check and possibly replace the space charater in paths
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-1579
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1579
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: harchive
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Mahadev konar
>
> Since the space character is used as a separator in the index files, it won't work if there are spaces in the path (see also HADOOP-6591).  The archive tools should 
> # detect if there are spaces in the paths and 
> # provide an option to replace it with some other characters.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.