[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Slacum updated ACCUMULO-391:
------------------------------------
Attachment: multi-table-if.patch
An initial crack at this.
I tried to have changes to existing code kept at a minimum, but I did have to:
- Make the configuration key strings for InputFormatBase public
- should be fine because they're final Strings
- Swapped some RecordReader method calls
- Made the RangeInputSplit actually use the table parameter passed to its
constructor
Instead of giving clients a Key/Value pair, this uses a TableKey, which is just
a key paired with a table name represented by a Text object. I didn't implement
per-table iterators.
> Multi-table Accumulo input format
> ---------------------------------
>
> Key: ACCUMULO-391
> URL: https://issues.apache.org/jira/browse/ACCUMULO-391
> Project: Accumulo
> Issue Type: New Feature
> Affects Versions: 1.4.0
> Reporter: John Vines
> Priority: Minor
> Attachments: multi-table-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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
