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

ASF subversion and git services commented on ACCUMULO-391:
----------------------------------------------------------

Commit 3227a822379718d6c1297f11d7af37a716f78a60 in branch 
refs/heads/ACCUMULO-391 from [~sonixbp]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=3227a82 ]

Adding the following:
- Deprecation to InputConfigurator, mapred.InputFormatBase, 
mapreduce.InputFormatBase
- Comments to TableQueryConfig
- Multi-table support to mapred.InputFormatBase

ACCUMULO-391


> 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