[
https://issues.apache.org/jira/browse/MAPREDUCE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742855#action_12742855
]
Chris K Wensel commented on MAPREDUCE-851:
------------------------------------------
I suspect Hive, Pig, etc will have the same issues. I'd prefer to not peek/poke
private fields via reflection and would like to see the api support
Configuration directly.
It could also be argued the static accessors should only know about
Configuration and nothing about Job, JobContext, etc types since it's there
business to set properties on the Configuration object.
I'm happy to submit a patch that mirrors all the accessors but accepts
Configuration. the current methods can be deprecated, or not. but would be
cleaner if they were removed at some point.
> Static job propery accessors don't accept Configuration but various
> JobContext sub-classes
> ------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-851
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-851
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.1
> Reporter: Chris K Wensel
>
> The current method of accepting only JobContext or one of its sub-classes
> adds much complexity to dynamic job configuration "builders" that manipulate
> the Configuration object in order to dynamically configure Hadoop jobs, and
> influence internal Hadoop sub-systems during runtime to provide higher level
> functions and features.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
