accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corey J. Nolet (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-391) Multi-table Accumulo input format
Date Wed, 25 Sep 2013 17:38:07 GMT


Corey J. Nolet commented on ACCUMULO-391:

[~keith_turner], I finished the requested changes last night locally and I implemented ACCUMULO-1732
as well. I do have an exception being thrown when a table being referenced in setRanges(),
addIterator(), or fetchColumns() has not been set- though it looks like the requested API
changes will fix that.

Anyways, I was going to push those up to the remote branch tonight. I also made the requested
formatting changes (and fixed intelli-j). I don't mind making some or all of the API changes
that we've discussed here but if you think it'd be better for you to implement them then I
don't mind that either. Anything I can do to help :-)
> 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