You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Billy Pearson (JIRA)" <ji...@apache.org> on 2009/03/06 18:55:56 UTC
[jira] Commented: (HBASE-1170) Specify startRow and stopRow for
MapReduce / TabieInputFormat
[ https://issues.apache.org/jira/browse/HBASE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679669#action_12679669 ]
Billy Pearson commented on HBASE-1170:
--------------------------------------
I thank we should have three options for this in TableMapReduceUtil
startRow only
stopRow only
startRow & stopRow
with that there should not be many reasons not use it and it would be more complete.
> Specify startRow and stopRow for MapReduce / TabieInputFormat
> -------------------------------------------------------------
>
> Key: HBASE-1170
> URL: https://issues.apache.org/jira/browse/HBASE-1170
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: mapred
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Fix For: 0.20.0
>
>
> We have a use case for this. Can currently be implemented using filters but this still requires a full table scan.
> In addition to extending TableMapReduceUtil, this would affect the splitting algorithm to only include those regions containing keys within the start and stop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.