[
https://issues.apache.org/jira/browse/ACCUMULO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776492#comment-13776492
]
Billie Rinaldi commented on ACCUMULO-391:
-----------------------------------------
Also it looks like TypedValueCombiner, TTimeoutTransport, and
core/src/test/resources/log4j.properties shouldn't be included in the patch.
Which IDE are you using? Something appears to be adding a space between a
method name and the parenthesis, e.g. "getInstance (" which doesn't match our
code style.
Also, it may be your IDE that has changed the AccumuloInputFormatTest to import
InputFormatBase.addIterator and other static methods instead of just
InputFormatBase, changing calls to this method from
AccumuloInputFormat.addIterator to just addIterator. I found this to be
confusing.
> 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
