You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Corey J. Nolet (JIRA)" <ji...@apache.org> on 2013/09/19 05:28:57 UTC

[jira] [Comment Edited] (ACCUMULO-391) Multi-table Accumulo input format

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

Corey J. Nolet edited comment on ACCUMULO-391 at 9/19/13 3:27 AM:
------------------------------------------------------------------

Patch for 1.6.0 branch. Let me know if you guys accept this and I'll merge my origin/ACCUMULO-391 branch over to master (I've already merged master into it so it's up to date as of right now).
                
      was (Author: sonixbp):
    Patch for 1.6.0 branch
                  
> 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 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