You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Scott Wang (JIRA)" <ji...@apache.org> on 2009/12/31 07:43:29 UTC

[jira] Created: (HBASE-2082) TableInputFormat is ignoring input scan's stop row setting

TableInputFormat is ignoring input scan's stop row setting
----------------------------------------------------------

                 Key: HBASE-2082
                 URL: https://issues.apache.org/jira/browse/HBASE-2082
             Project: Hadoop HBase
          Issue Type: Bug
          Components: mapreduce
    Affects Versions: 0.20.2
            Reporter: Scott Wang


In the getSplits() function of TableInputFormatBase, there is a line to compare the region's stop key and the given scan's stop key.

If the region's stop key is smaller, then use the region's stop key instead of the one given by user.

But the last region will not have a stop key, so comparing a null key to the given stop key  is always smaller, and the user's stop key is simply ignored.

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


[jira] Updated: (HBASE-2082) TableInputFormat is ignoring input scan's stop row setting

Posted by "Scott Wang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Wang updated HBASE-2082:
------------------------------

    Attachment: HBASE-2082.patch

my patch to this bug

> TableInputFormat is ignoring input scan's stop row setting
> ----------------------------------------------------------
>
>                 Key: HBASE-2082
>                 URL: https://issues.apache.org/jira/browse/HBASE-2082
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.20.2
>            Reporter: Scott Wang
>         Attachments: HBASE-2082.patch
>
>
> In the getSplits() function of TableInputFormatBase, there is a line to compare the region's stop key and the given scan's stop key.
> If the region's stop key is smaller, then use the region's stop key instead of the one given by user.
> But the last region will not have a stop key, so comparing a null key to the given stop key  is always smaller, and the user's stop key is simply ignored.

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


[jira] Resolved: (HBASE-2082) TableInputFormat is ignoring input scan's stop row setting

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-2082.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
                   0.20.3
         Assignee: Scott Wang
     Hadoop Flags: [Reviewed]

Committed to 0.20 branch and trunk. Thanks for the patch Scott!

> TableInputFormat is ignoring input scan's stop row setting
> ----------------------------------------------------------
>
>                 Key: HBASE-2082
>                 URL: https://issues.apache.org/jira/browse/HBASE-2082
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.20.2
>            Reporter: Scott Wang
>            Assignee: Scott Wang
>             Fix For: 0.20.3, 0.21.0
>
>         Attachments: HBASE-2082.patch
>
>
> In the getSplits() function of TableInputFormatBase, there is a line to compare the region's stop key and the given scan's stop key.
> If the region's stop key is smaller, then use the region's stop key instead of the one given by user.
> But the last region will not have a stop key, so comparing a null key to the given stop key  is always smaller, and the user's stop key is simply ignored.

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