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

Corey J. Nolet commented on ACCUMULO-391:
-----------------------------------------

I have the requested API changes in origin/ACCUMULO-391 if anyone would
like to review them. I have held off on deprecating the old methods until
there is consensus to do so.


On Mon, Sep 30, 2013 at 8:09 PM, ASF subversion and git services (JIRA) <



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

Reply via email to