[ https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796240#comment-13796240 ]
ASF subversion and git services commented on ACCUMULO-391: ---------------------------------------------------------- Commit 9a63ff4ecf4b479403d16f1ee44b4f552f71719d in branch refs/heads/master from [~sonixbp] [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=9a63ff4 ] ACCUMULO-391 setters and getters for BatchScanConfigs on jobs now use Map<String,BatchScanConfig> instead of a vararg. > 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)