accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-391) Multi-table Accumulo input format
Date Wed, 25 Sep 2013 15:18:03 GMT


Keith Turner commented on ACCUMULO-391:

bq.  There's nothing tying us to the current method of configuring jrrbs

What are "jrrbs"?

bq.  I wouldn't worry about having things configured for tables that aren't going to be scanned.
 I can't see a bug happening from it that wouldn't be caught with minimal exercise/testing.

I am pretty sure people will end up spending lots of time trying to figure out why their scan
time iterators are not being executed because they mistyped a table name.  I agree that they
will most likely hit this while testing, but its still wasting a developers time.  
> 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