[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753619#comment-13753619
]
Corey J. Nolet edited comment on ACCUMULO-391 at 8/29/13 1:32 PM:
------------------------------------------------------------------
Agreed- I've got a remote branch pushed up last night with the initial patch
applied as-is. The refactor of the constants into the MetadataSchema, the
removal of the ContextFactory, and a couple other small changes broke the
patch. I'm working through getting the tests running in their current state and
I'll work through modifying the current InputFormatBase to provide multi-table
support (and satisfying your comments above).
was (Author: sonixbp):
Agreed- I've got a remote branch pushed up last night with the initial
patch applied as-is. The refactor of the constants into the MetadataSchema, the
removal of the ContextFactory, and a couple other small changes broke the
patch. I'm working through getting the tests running in their current state and
I'll work through modifying the current InputFormatBase to provide multi-table
support.
> 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
