[
https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797212#action_12797212
]
Rodrigo Schmidt commented on HDFS-684:
--------------------------------------
This patch needs hadoop-...-tools.jar and I didn't know how to change raid's
build.xml file just to add hadoop-...-tools.jar to the classpath without
redefining the whole classpath and all the other targets.
To make the patch compile and run the unit tests in my computer I just copied
hadoop-...-tools.jar to [HADOOP_HOME]/lib, but I know this is not the best
thing to do and that's why it failed Hadoop QA.
What's the most non-intrusive way to change raid's build.xml file in this case?
> Use HAR filesystem to merge parity files
> -----------------------------------------
>
> Key: HDFS-684
> URL: https://issues.apache.org/jira/browse/HDFS-684
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: contrib/raid
> Reporter: dhruba borthakur
> Assignee: Rodrigo Schmidt
> Attachments: HDFS-684.0.patch, HDFS-684.1.patch
>
>
> The HDFS raid implementation (HDFS-503) creates a parity file for every file
> that is RAIDed. This puts additional burden on the memory requirements of the
> namenode. It will be nice if the parity files are combined together using
> the HadoopArchive (har) format.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
