accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <>
Subject [jira] [Comment Edited] (ACCUMULO-391) Multi-table Accumulo input format
Date Tue, 24 Sep 2013 16:39:05 GMT


Billie Rinaldi edited comment on ACCUMULO-391 at 9/24/13 4:38 PM:

Anyone have comments on using TableKey vs. a plain Key?

Nevermind, it looks like TableKey is still there but isn't being used.  I'm still looking
over the patch, but the only comment I have so far is that it seems to include diffs for a
couple of files it shouldn't.
      was (Author: billie.rinaldi):
    Anyone have comments on using TableKey vs. a plain Key?
> Multi-table Accumulo input format
> ---------------------------------
>                 Key: ACCUMULO-391
>                 URL:
>             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:

View raw message