[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791000#comment-13791000
]
Eric Newton edited comment on ACCUMULO-391 at 10/9/13 11:49 PM:
----------------------------------------------------------------
+1 for separate classes for just simpler ease-of-use.
+1 for reusing the multitable implementation if it doesn't decrease performance
I think it's tough on users to deprecate the interface they are used to for a
(slightly) more complicated interface they probably don't need.
was (Author: ecn):
+1 for separate classes for just simpler ease-of-use.
+1 for reusing the multitable implementation if it doesn't decrease performance
I think it's tough on users to deprecate the interface they are used to for a
(slightly) more complicated interface they probably don't.
> Multi-table Accumulo input format
> ---------------------------------
>
> Key: ACCUMULO-391
> URL: https://issues.apache.org/jira/browse/ACCUMULO-391
> Project: Accumulo
> Issue Type: New Feature
> Reporter: John Vines
> Assignee: Corey J. Nolet
> Priority: Minor
> Labels: mapreduce,
> Fix For: 1.6.0
>
> Attachments: ACCUMULO-391.patch, multi-table-if.patch,
> new-multitable-if.patch
>
>
> Just realized we had no MR input method which supports multiple Tables for an
> input format. I would see it making the table the mapper's key and making the
> Key/Value a tuple, or alternatively have the Table/Key be the key tuple and
> stick with Values being the value.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
