hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Telford (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5208) Allow setting Scan start/stop row individually in TableInputFormat
Date Mon, 16 Jan 2012 18:49:39 GMT

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

Nicholas Telford commented on HBASE-5208:
-----------------------------------------

That was my intention. I can extract that out to an intermediary method if that's preferable,
however that doesn't really solve the problem that doubling the number of MR jobs spun up
causes the test to timeout. Any ideas on that one?
                
> 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
>
>
> 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

        

Mime
View raw message