[
https://issues.apache.org/jira/browse/MAPREDUCE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194270#comment-13194270
]
Ravi Prakash commented on MAPREDUCE-3736:
-----------------------------------------
Just to make things more explicit. Amar found
(https://issues.apache.org/jira/browse/MAPREDUCE-3462?focusedCommentId=13175250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13175250)
bq. I tried setting this property in src/test/mapred-site.xml but the test
still failed. Somehow, we should make sure that the contrib tests load the
src/test/mapred-site.xml.
This is a pretty basic property and I don't think we can do without it. So even
for tests it needs to be defined. I could do a git bisect to see what changed,
but mehhh.....
{noformat}
_______________________
< I'm too lazy for that >
-----------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
{noformat}
> Variable substitution depth too large for fs.default.name causes jobs to fail
> -----------------------------------------------------------------------------
>
> Key: MAPREDUCE-3736
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3736
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Eli Collins
> Assignee: Ahmed Radwan
> Priority: Blocker
>
> I'm seeing the same failure as MAPREDUCE-3462 in downstream projects running
> against a recent build of branch-23. MR-3462 modified the tests rather than
> fixing the framework. In that jira Ravi mentioned "I'm still ignorant of the
> change which made the tests start to fail. I should probably understand
> better the reasons for that change before proposing a more generalized fix."
> Let's figure out the general fix (rather than require all projects to set
> mapreduce.job.hdfs-servers in their conf we should fix this in the
> framework). Perhaps we should not default this config to "$fs.default.name"?
--
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
