[
https://issues.apache.org/jira/browse/HBASE-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432481#comment-13432481
]
Lars Hofhansl commented on HBASE-3996:
--------------------------------------
Looking at it again and reviewing the comments and the latest version of RB
this looks good. Not sure why it got stuck.
A remaining question is 0.94 or not. The changes to TableSplit would not allow
a new version of it to be deserialized by an old server. Is that OK for an M/R
job?
Also, the comment I had about that extra table.close
TableRecordReaderImpl.java. If that is a bug I would prefer that in a separate
jira (unless other changes here necessitate this close, but I do not think so).
@Stack: Could you make sure that your comments are addressed?
> Support multiple tables and scanners as input to the mapper in map/reduce jobs
> ------------------------------------------------------------------------------
>
> Key: HBASE-3996
> URL: https://issues.apache.org/jira/browse/HBASE-3996
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Eran Kutner
> Assignee: Eran Kutner
> Fix For: 0.96.0, 0.94.2
>
> Attachments: 3996-v2.txt, 3996-v3.txt, 3996-v4.txt, 3996-v5.txt,
> 3996-v6.txt, 3996-v7.txt, HBase-3996.patch
>
>
> It seems that in many cases feeding data from multiple tables or multiple
> scanners on a single table can save a lot of time when running map/reduce
> jobs.
> I propose a new MultiTableInputFormat class that would allow doing this.
--
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