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

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 <[EMAIL PROTECTED]> 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