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 18:14:02 GMT


Keith Turner commented on ACCUMULO-391:

bq.  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.

I only wanted to pick it up if you were not interested.  I do not have a specific solution
in mind.   [~bills] raises a good point. If the java API is improved, it may not be possible
to misconfigure through the API but a user could still create a wacky config by setting properties
directly on the job config.  So we will still need to sanity check the config and it sounds
like you may already have that done.
> 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