[
https://issues.apache.org/jira/browse/HBASE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars George updated HBASE-1829:
-------------------------------
Attachment: HBASE-1829-v2.patch
HBASE-1829-v2.patch fixes error Stack got above. Comparing cannot be done with
KeyValue comparators but Bytes.compareTo() directly. Also fixed issues with
start and stop row. Scan by default has a value assigned to them and does not
return "null". Comparing to HConstants.EMPTY_START_ROW for example did not
work, so I chose checking the length instead.
Tested with a real data set and it works for subrange and full scan. Will still
add unit test. Just thought I up the patch here for progress tracking.
> 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.
