accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-695) Make input and output formats support the old mapreduce api again
Date Wed, 12 Dec 2012 21:51:21 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530387#comment-13530387
] 

Christopher Tubbs commented on ACCUMULO-695:
--------------------------------------------

I would argue against doing it in the same classes, because I don't think users familiar with
one and not the other, should be bombarded with available API methods that aren't suitable
to the framework of their choice. Further, each framework has separate design goals, documentation,
and examples, and it could be confusing to both developers and users to maintain these in
a single set of classes.
                
> Make input and output formats support the old mapreduce api again
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-695
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-695
>             Project: Accumulo
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.1, 1.3.6
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>             Fix For: 1.5.0
>
>
> It might be possible to do this with single classes that support both, e.g.
> class InputFormatBase<K,V> extends InputFormat<K,V> implements org.apache.hadoop.mapred.InputFormat<K,V>.

--
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

Mime
View raw message