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

Hudson commented on FLUME-1920:
-------------------------------

UNSTABLE: Integrated in flume-trunk #650 (See 
[https://builds.apache.org/job/flume-trunk/650/])
FLUME-1920. Remove Hadoop dependency from integration tests (mpercy: 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=0c5b87a5dfd53bcdcf8e2d8c570735573cd274ad)
* flume-ng-tests/src/test/java/org/apache/flume/test/agent/TestFileChannel.java
* flume-ng-tests/src/test/java/org/apache/flume/test/util/StagedInstall.java


> Test case TestFileChannel fails when flume is built from paths containing the 
> string "hadoop"
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLUME-1920
>                 URL: https://issues.apache.org/jira/browse/FLUME-1920
>             Project: Flume
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: v1.3.0, v1.4.0, v1.3.1, v1.5.0, v1.6.0
>            Reporter: Aline Guedes Pinto
>            Assignee: li xiang
>            Priority: Minor
>             Fix For: v1.6.0
>
>         Attachments: FLUME-1920-1.patch, FLUME-1920-2.patch, FLUME-1920.patch
>
>
> When flume is built from a path that contains the string "hadoop" (ie: 
> /home/user/hadoop_components/flume), the test case TestFileChannel fails.
> The reason it fails is because it can't find the correct location of the 
> hadoop jar file - the function findHadoopJar in TestFileChannel.java 
> looks for the hadoop jar path by searching for the string "hadoop" in the 
> property java.class.path, and returns the first match of the search. 
> This is not necessarily the correct location of the hadoop jar.
> The right thing to do is to look for the name of the hadoop jar in the 
> classpath (ie: hadoop-core-1.1.1.jar), instead of looking for the string 
> "hadoop".



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to