accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ACCUMULO-391) Multi-table Accumulo input format
Date Tue, 24 Sep 2013 02:29:03 GMT

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

Keith Turner edited comment on ACCUMULO-391 at 9/24/13 2:28 AM:
----------------------------------------------------------------

A few thoughts

* Why deprecate setting a single input table?  This is a common use case.
* I think table should come after job in method parameters.   Like addIterator(job, table,
iterCfg) instead of addIterator(job, iterCfg, table).  
* What happens if I configure iterators for a table that I did not set as an input?

Also, some formatting changes like the following seem odd.

{noformat}
-    InputConfigurator.setAutoAdjustRanges(CLASS, job, enableFeature);
+    InputConfigurator.setAutoAdjustRanges (CLASS, job, enableFeature);
{noformat}



                
      was (Author: kturner):
    A few thoughts

* Why deprecate setting a single input table?  This is a common use case.
* I think table should come after job in method parameters.   Like addIterator(job, table,
iterCfg) instead of addIterator(job, iterCfg, table).  
* What happens if I configure iterators for a table that I did not set as an input?

Also, some formatting changes like the following seem odd.

-    InputConfigurator.setAutoAdjustRanges(CLASS, job, enableFeature);
+    InputConfigurator.setAutoAdjustRanges (CLASS, job, enableFeature);



                  
> 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

Mime
View raw message