[
https://issues.apache.org/jira/browse/HADOOP-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591442#action_12591442
]
Dennis Kubes commented on HADOOP-3261:
--------------------------------------
Sure, I will make the changes. I just wanted to give an example of possibility
before and I saw that ReflectionUtils was used all over the codebase and didn't
know if having a DI creator in that class would have unintended side effects.
One other thing. We may not want to limit this to just spring. The ability to
create these classes and others could be handled in a number of different ways
by different frameworks, spring, guice, etc. I think it is something to think
about.
> Allow Mapper and Reducer classes to be created a Spring Beans
> -------------------------------------------------------------
>
> Key: HADOOP-3261
> URL: https://issues.apache.org/jira/browse/HADOOP-3261
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Environment: All
> Reporter: Dennis Kubes
> Assignee: Dennis Kubes
> Attachments: HADOOP-3261-1-20080415.patch, spring.jar
>
>
> This improvement abstracts the creation of Mappers and Reducers in factory
> classes and adds the ability to define a spring beans.xml file in the
> classpath and have the Mapper and Reducer classes be created as spring beans.
> This is transparent to the rest of Hadoop but the benefit is that is allows
> Mapper and Reducer classes to have their dependencies injected versus having
> them hardcoded. This will help in the ability to test various mapreduce jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
