[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783194#comment-13783194
]
Corey J. Nolet commented on ACCUMULO-391:
-----------------------------------------
That's a great question Josh. Originally, I changed the @since tags to
1.6.0 but since I only changed a few lines in the method, I couldn't
justify the change to the javadoc. It would be nice if we could define a
general practice for this.
On another note- are we planning on deprecating the existing legacy methods
for adding input to a single table? I'll add those in before I merge as
well but I wanted to make sure that's what everyone wanted.
> 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 was sent by Atlassian JIRA
(v6.1#6144)
