[
https://issues.apache.org/jira/browse/ACCUMULO-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659760#comment-13659760
]
Billie Rinaldi commented on ACCUMULO-1421:
------------------------------------------
Putting the getConfiguration(JobContext) method in InputFormatBase makes it
part of the public API. Should we consider making a
core.util.CompatibilityLayer class where we could put stuff like this, and then
it will be easy to get rid of it when we no longer need it?
Do we want this in 1.5 yet, or just trunk? It will only be needed when we've
tracked down all the incompatibilities. And if their fixes are all
non-API-changing like this, it will be an easy decision to merge them to 1.5
given the benefits. On the other hand ... if it's possible that we might only
support hadoop 2 for 1.6, then we only want this fix in 1.5. I guess there's
no way to predict that at this point.
> use reflection to improve compatibility between Hadoop 1 and 2 JobContext
> objects
> ---------------------------------------------------------------------------------
>
> Key: ACCUMULO-1421
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1421
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Adam Fuchs
> Assignee: Adam Fuchs
>
> JobContext switches between an abstract class and an interface in hadoop 1
> and 2, causing runtime compatibility problems in the compiled Accumulo
> bytecode. Avoid the runtime problem by using reflection to access the
> configuration object stored in the JobContext.
--
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
