You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org> on 2012/01/16 15:22:39 UTC
[jira] [Commented] (HBASE-5208) Allow setting Scan start/stop row
individually in TableInputFormat
[ https://issues.apache.org/jira/browse/HBASE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186936#comment-13186936 ]
Hadoop QA commented on HBASE-5208:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12510704/HBASE-5208-001.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/776//console
This message is automatically generated.
> Allow setting Scan start/stop row individually in TableInputFormat
> ------------------------------------------------------------------
>
> Key: HBASE-5208
> URL: https://issues.apache.org/jira/browse/HBASE-5208
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Nicholas Telford
> Priority: Minor
> Attachments: HBASE-5208-001.txt
>
>
> Currently, TableInputFormat initializes a serialized Scan from "hbase.mapreduce.scan". Alternatively, it will instantiate a new Scan using properties defined in "hbase.mapreduce.scan.*". However, of these properties the "start row" and "stop row" (arguably the most pertinent) are missing.
> TableInputFormat should permit the specification of a start/stop row as with the other fields using a new pair of properties: "hbase.mapreduce.scan.row.start" and "hbase.mapreduce.scan.row.end"
> The primary use-case for this is to permit Oozie and other job management tools that can't call TableMapReduceUtil.initTableMapperJob() to operate on a contiguous subset of rows.
--
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