Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 16 Jun 2012 02:49:43 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <99388370.21112.1339814983128.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <209596672.44019.1329353100644.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3868) Reenable Raid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on MAPREDUCE-3868:
-----------------------------------------------

most of the patch is just moving files around, doing that with 'patch' will delete/create those files and subversion will not know bind them. This means that all changes prior this this JIRA will be lost as all the moved files will be (from SVN perspective) new files. you won't be able to track previous changes directly. The original patch I've submitted as a script/combo patch, the script does 'svn mv' which tells SVN to bind the files in the new location with the old location thus allowing you to trace changes to the first commit of the files. the script works both in filesystem and SVN mode.
                
> Reenable Raid
> -------------
>
>                 Key: MAPREDUCE-3868
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3868
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: contrib/raid
>            Reporter: Scott Chen
>            Assignee: Weiyan Wang
>         Attachments: MAPREDUCE-3868-1.patch, MAPREDUCE-3868.patch, MAPREDUCE-3868v1.patch, MAPREDUCE-3868v1.sh
>
>
> Currently Raid is outdated and not compiled. Make it compile.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira