hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris K Wensel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1605) TableInputFormat should support 'limit'
Date Thu, 02 Jul 2009 18:01:47 GMT

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

Chris K Wensel commented on HBASE-1605:

Nope, doesn't look like it. I'm not calling for a configurable number of mappers/splits. 

But asking the total number of rows returned across all splits be exactly equal to an optional
'limit' value.

And pointing out the current impl, as I see it in trunk, sets the splits to the number of
regions in a table thus implying that a single global Filter across all splits won't work
as limit may not be evenly divided among the splits.

It will be nice to specify the number of mappers/splits and have it honored though.

> TableInputFormat should support 'limit'
> ---------------------------------------
>                 Key: HBASE-1605
>                 URL: https://issues.apache.org/jira/browse/HBASE-1605
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Chris K Wensel
> Would be useful if TableInputFormat could be passed a 'limit' property value that limited
the total result set to the value of 'limit'.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message