[ https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765045#comment-13765045 ]
ASF subversion and git services commented on ACCUMULO-391: ---------------------------------------------------------- Commit e781879d217476793c18725476453a58e9258d02 in branch refs/heads/ACCUMULO-391 from [~sonixbp] [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=e781879 ] Pulled William Slacum's multi-table input format into the current design with the InputConfigurator. 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: 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira