[
https://issues.apache.org/jira/browse/HBASE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764317#action_12764317
]
Lars George commented on HBASE-1829:
------------------------------------
Hey Ken,
I assumed that it will only really send in the rows between start row
(inclusive) and stop row (exclusive) because the TIF uses the Scan instance to
scan the actual table and setting these two values should enforce the
boundaries.
I was travelling the last few days and did not get much done. I was in the
process of adding a unit test for the change that should show that it selects
the right regions as well as enforce the start/stop row boundaries. I will see
that I get that done asap. If it passes it is all ready to go.
> Make use of start/stop row in TableInputFormat
> ----------------------------------------------
>
> Key: HBASE-1829
> URL: https://issues.apache.org/jira/browse/HBASE-1829
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Lars George
> Assignee: Lars George
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HBASE-1829-v2.patch, HBASE-1829.patch
>
>
> Since we can now specify a start and stop row with the Scan that is handed to
> the TIF we can reduce the splits to the regions that contain these rows. That
> allows to test large MR jobs on a single region for example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
