[jira] [Commented] (HBASE-5208) Allow setting Scan start/stop row individually in TableInputFormat

["Nick Dimiduk (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589953#comment-13589953 ] 

Nick Dimiduk commented on HBASE-5208:
-------------------------------------

This first release I see containing this addition is 0.94.0. Marking as appropriate and resolving.

{noformat}
$ git grep 'hbase\.mapreduce\.scan\.row\.start' $(git tag -l | grep 0\.9\\d.\\d$)
0.94.0:src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormat.java:  public static final String SCAN_ROW_START = "hbase.mapreduce.scan.row.start";
...
{noformat}
                
> 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, 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