hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1322) TestStreamingAsDifferentUser fails on trunk
Date Tue, 22 Dec 2009 08:20:29 GMT

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

Devaraj Das updated MAPREDUCE-1322:

    Attachment: 1322.patch

My initial thought on this one was that this config doesn't require to be tweaked at all (even
by admins). It should typically point to "/user". But for testing purposes, i wanted to have
it point to some temp dir. It didn't strike me that streaming tests don't pick the conf up
from src/test. 
After thinking about it some more, i think it makes sense to indeed define the config in mapred-default.xml.

Attaching a patch.

> TestStreamingAsDifferentUser fails on trunk
> -------------------------------------------
>                 Key: MAPREDUCE-1322
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1322
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/streaming, test
>    Affects Versions: 0.22.0
>            Reporter: Amareshwari Sriramadasu
>             Fix For: 0.22.0
>         Attachments: 1322.patch
> TestStreamingAsDifferentUser fails on trunk with following exception :
> Can not create a Path from a null string
> java.lang.IllegalArgumentException: Can not create a Path from a null string
> 	at org.apache.hadoop.fs.Path.checkPathArg(Path.java:78)
> 	at org.apache.hadoop.fs.Path.<init>(Path.java:90)
> 	at org.apache.hadoop.mapred.ClusterWithLinuxTaskController.createHomeAndStagingDirectory(ClusterWithLinuxTaskController.java:158)
> 	at org.apache.hadoop.mapred.ClusterWithLinuxTaskController.startCluster(ClusterWithLinuxTaskController.java:147)
> 	at org.apache.hadoop.streaming.TestStreamingAsDifferentUser.testStreaming(TestStreamingAsDifferentUser.java:49)
> The corresponding line for the exception :
> {code}
>     Path stagingArea = new Path(conf.get(JTConfig.JT_STAGING_AREA_ROOT));
> {code}

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

View raw message