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 14:54:03 GMT


Keith Turner commented on ACCUMULO-391:

bq. What do you think about taking the union of all the tables configured as input tablets,
or with ranges, iterators, or fetched columns?

I think this may be easier to use but more error prone.  There are more places where you can
mistype a table name.  

A fluent class for configuring tables to read would be another alternative.  The class could
serialize itself to job or a static method could take job and varargs of these table config
classes.  This completely eliminates the problem from the API, the API does not allow setting
configuration for a table you are not reading and the table name is only specified once (in
the constructor of the config object).  

> 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