David,
> It looks like calling configuration.setBoolean("mapred.task.profile",
> true) will enable profiling with the 20.2 APIs. I am able to see the
> profiling output when I check the web interface. Thanks for your help! Is
> there a good place to document this setting so others can find th
[BCC-ing "general" - again.]
On Tuesday 17 August 2010 07:36 AM, Scott Whitecross wrote:
Thanks for the answers Doug and Arun. I'm assuming the job-history files
mentioned are in ./hadoop-0.20/logs/history/done/. The files look like they
were serialized by a class in Hadoop? (If I can read t
You're right.
You need to specify a mapper.
On Mon, Aug 16, 2010 at 3:21 PM, David Rosenstrauch wrote:
> On 08/16/2010 05:48 PM, Ted Yu wrote:
>
>> No.
>>
>> On Mon, Aug 16, 2010 at 1:25 PM, David Rosenstrauch> >wrote:
>>
>> Is it possible for a M/R job to have no mapper? i.e.:
>>> job.setMappe
On 08/16/2010 05:48 PM, Ted Yu wrote:
No.
On Mon, Aug 16, 2010 at 1:25 PM, David Rosenstrauchwrote:
Is it possible for a M/R job to have no mapper? i.e.:
job.setMapperClass(null)? Or is it required that one at least use an
"identity mapper" (i.e., plain vanilla org.apache.hadoop.mapreduce.Ma
No.
On Mon, Aug 16, 2010 at 1:25 PM, David Rosenstrauch wrote:
> Is it possible for a M/R job to have no mapper? i.e.:
> job.setMapperClass(null)? Or is it required that one at least use an
> "identity mapper" (i.e., plain vanilla org.apache.hadoop.mapreduce.Mapper)?
>
> Thanks,
>
> DR
>
Hi Hemanth,
It looks like calling configuration.setBoolean("mapred.task.profile",
true) will enable profiling with the 20.2 APIs. I am able to see the
profiling output when I check the web interface. Thanks for your help! Is
there a good place to document this setting so others can find this
Is it possible for a M/R job to have no mapper? i.e.:
job.setMapperClass(null)? Or is it required that one at least use an
"identity mapper" (i.e., plain vanilla org.apache.hadoop.mapreduce.Mapper)?
Thanks,
DR
