[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777611#comment-13777611
]
William Slacum commented on ACCUMULO-391:
-----------------------------------------
"jrrbs" == "jobs." As in, "They took our jrrbs!"
Even so, the case of debugging that only has the issue you're talking about
will only happen when someone is just using raw strings as the arguments and
not a variable. Until the mechanism to configure jobs isn't just applying
partial mutations to a {{Configuration}} object, we're doing to deal with
issues like this, even in a single table case. Any hardening of the API should
happen after we've at least added this feature so that we have it now and can
consider it for the API change.
> 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
