You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2013/02/28 23:47:13 UTC
[jira] [Closed] (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:all-tabpanel ]
Lars Hofhansl closed HBASE-5208.
--------------------------------
> 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
> Fix For: 0.94.0
>
> Attachments: HBASE-5208-001.txt, HBASE-5208-002.txt, HBASE-5208-003.txt, HBASE-5208-004.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
For more information on JIRA, see: http://www.atlassian.com/software/jira