[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781227#comment-13781227
]
ASF subversion and git services commented on ACCUMULO-391:
----------------------------------------------------------
Commit fca2731f28827d54514188ac8334ad6f714b12df in branch
refs/heads/ACCUMULO-391 from [~sonixbp]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=fca2731 ]
The original single-table setters/getters now populate a "default"
TableQueryConfig object under the hood. This should make the switch over much
easier. Deprecated single table methods in light of the API changes for the new
configuration object. 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)
