Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of donofrio111@gmail.com
 designates 209.85.128.182 as permitted sender)
Message-ID: <5118A088.5040407@gmail.com>
Date: Mon, 11 Feb 2013 02:40:56 -0500
From: Jim Donofrio <donofrio111@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: user@hadoop.apache.org
Subject: Re: why does OldCombinerRunner pass Reporter.NULL to the combiner
 instead of the real reporter?
References: <5113AEC8.6000208@gmail.com>
 <CAOcnVr0NTGqrs99TTFSvHyZY=kZWA3dnFaZURG4aR2aBKTRdtw@mail.gmail.com>
In-Reply-To: 
 <CAOcnVr0NTGqrs99TTFSvHyZY=kZWA3dnFaZURG4aR2aBKTRdtw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I submitted MAPREDUCE-4998 with a patch

On 02/07/2013 11:18 AM, Harsh J wrote:
> I agree its a bug if there is a discrepancy between the APIs (we are
> supposed to be supporting both for the time being). Please do file a
> JIRA with a patch - there shouldn't be any harm in re-passing the
> reporter object within the combiner.
>
> On Thu, Feb 7, 2013 at 7:10 PM, Jim Donofrio <donofrio111@gmail.com> wrote:
>> Is there a good reason why the OldCombinerRunner passes Reporter.NULL to the
>> combiner instead of the actual TaskReporter? The NewCombinerRunner does use
>> the TaskReporter when creating the context. If this is a bug I will submit a
>> JIRA with a patch
>
>
> --
> Harsh J
>