[ https://issues.apache.org/jira/browse/HBASE-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247444#comment-13247444 ]
Eran Kutner commented on HBASE-3996: ------------------------------------ @stack: I believe the only open issue in the review board is your suggestion to replace my MultiTableInputCollection with a List<Scan>. Although I agree it would make the patch simpler and allow it to have one less class, I think it will make using it less natural. Developers will have to create a Scan which is a common object and then set a table attribute. This feels less natural to me than setting the table by adding to a collection the way I've done it, but I guess it's a matter of perspective. > 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 > > 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