Hey all
Have some users reporting intermittent spawning of Reducers when the
job.xml shows mapred.reduce.tasks=0 in 0.19.0 and .1.
This is also confirmed when jobConf is queried in the (supposedly
ignored) Reducer implementation.
In general this issue would likely go unnoticed since the default
reducer is IdentityReducer.
but since it should be ignored in the Mapper only case, we don't
bother not setting the value, and subsequently comes to ones attention
rather abruptly.
am happy to open a JIRA, but wanted to see if anyone else is
experiencing this issue.
note the issue seems to manifest with or without spec exec.
ckw
--
Chris K Wensel
ch...@wensel.net
http://www.cascading.org/
http://www.scaleunlimited.com/
