[ 
https://issues.apache.org/jira/browse/HDFS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Boudnik updated HDFS-475:
------------------------------------

    Attachment: HDFS-475.patch

The patch adds the following high level targets:
- jar-fi                     Make hadoop-fi.jar
- jar-hdfs-test-fi           Make hadoop-test-fi.jar
- jar-hdfswithmr-test-fi     Make hadoop-test-fi.jar
- jar-test-fi                Make hadoop-test.jar
- run-test-hdfs-fi           Run FI related hdfs tests
- run-test-hdfs-with-mr-fi   Run hdfs FI related unit tests that require mapred


> Create a separate targets for fault injection related test and jar files 
> creation files
> ---------------------------------------------------------------------------------------
>
>                 Key: HDFS-475
>                 URL: https://issues.apache.org/jira/browse/HDFS-475
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.21.0
>
>         Attachments: HDFS-475.patch, HDFS-475.patch
>
>
> Current implementation of the FI framework allows to mix faults into 
> production classes, e.g. into build/ folder.
> Although the default probability level is set to zero it doesn't look clean 
> and might potentially over complicate the build and release process.
> FI related targets are better be logically and physically separated, e.g. to 
> put instrumented artifacts into a separate folder, say, build-fi/

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

Reply via email to