[
https://issues.apache.org/jira/browse/MRUNIT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466828#comment-13466828
]
Jim Donofrio commented on MRUNIT-114:
-------------------------------------
Just to clarify, are you saying that the mapred KeyFieldBasedComparator will
only get configured with a JobConf object and not a Configuration object? I
guess we could work around that but hadoop will act the same way but if you are
using mapred, hadoop forces you to submit JobConf at some point, maybe we
should do the same?
> should support calling configure on sorting and grouping comparators if
> applicable
> ----------------------------------------------------------------------------------
>
> Key: MRUNIT-114
> URL: https://issues.apache.org/jira/browse/MRUNIT-114
> Project: MRUnit
> Issue Type: Bug
> Reporter: Jacob Metcalf
> Assignee: Jim Donofrio
> Fix For: 1.0.0
>
>
> From Jacob Metcalf:
> On another subject (maybe I need a new thread/JIRA for this) is it
> intentional that the configuration is not applied to the sorting and grouping
> comparators?
> I am writing my own multiple input MR driver to test a reduce side join and
> had to do:
> // Configure grouping and sorting comparators
> if (keyGroupComparator instanceof Configured ) {
> ((Configured)keyGroupComparator).setConf( configuration );
> }
> if (keyValueOrderComparator instanceof Configured) {
> ((Configured)keyValueOrderComparator).setConf( configuration );
> }
> To get the config applied even though they are Configured objects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
