hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-665) server side scanner doesn't honor stop row
Date Fri, 06 Jun 2008 05:04:45 GMT

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

stack commented on HBASE-665:
-----------------------------

Part of the problem here, I think, is the scanner client side is dumb to the stop row.  Here's
what I see w/ client-side debug enabled (Before Clint's patch):

{code}
hbase> c = HBaseConfiguration.new()#<Java::OrgApacheHadoopHbase::HBaseConfiguration:0xf549de
@java_object=Configuration: hadoop-default.xml, hadoop-site.xml, hbase-default.xml, hbase-site.xml>hbase>
t = HTable.new(c, "TestTable")08/06/06 05:01:22 DEBUG client.HConnectionManager$TableServers:
Found ROOT regionname: -ROOT-,,0, startKey: <>, endKey: <>, encodedName: 70236052,
tableDesc: {name: -ROOT-, families: [{name: info, max versions: 1, compression: NONE, in memory:
false, block cache enabled: false, max length: 2147483647, time to live: FOREVER, bloom filter:
none}]}#<Java::OrgApacheHadoopHbaseClient::HTable:0x5f7d3f @java_object=org.apache.hadoop.hbase.client.HTable@117b450>hbase>
columns = ["info:"].to_java(java.lang.String)#<#<Class:01xb398da>:0xf84b0a @java_object=[Ljava.lang.String;@106b56a>
hbase> s = t.getScanner(columns, "", "0000000003", HConstants::LATEST_TIMESTAMP).iterator()
08/06/06 04:34:05 DEBUG client.HTable$ClientScanner: Creating scanner over TestTable starting
at key ''
08/06/06 04:34:05 DEBUG client.HTable$ClientScanner: Advancing internal scanner to startKey
at
08/06/06 04:34:05 DEBUG client.HConnectionManager$TableServers: Cache hit in table locations
for row <> and tableName TestTable: location server 208.76.44.141:60020, location region
name TestTable,,1212686166322
#<#<Class:01x37504d>:0x178feba @java_object=org.apache.hadoop.hbase.client.HTable$ClientScanner$1@81933a>
hbase> s.each do |r|
?>     puts String.from_java_bytes r.getRow()
hbase> end
0000000000
0000000001
0000000002
08/06/06 04:34:05 DEBUG client.HTable$ClientScanner: Advancing forward from region regionname:
TestTable,,1212686166322, startKey: <>, endKey: <0001086183>, encodedName: 591865778,
tableDesc: {name: TestTable, families: [{name: info, max versions: 3, compression: NONE, in
memory: false, block cache enabled: false, max length: 2147483647, time to live: FOREVER,
bloom filter: none}]}
08/06/06 04:34:05 DEBUG client.HTable$ClientScanner: Advancing internal scanner to startKey
at 0001086183
08/06/06 04:34:05 DEBUG client.HTable$ClientScanner: Advancing forward from region regionname:
TestTable,0001086183,1212686166323, startKey: <0001086183>, endKey: <0003154574>,
encodedName: 1619485603, tableDesc: {name: TestTable, families: [{name: info, max versions:
3, compression: NONE, in memory: false, block cache enabled: false, max length: 2147483647,
time to live: FOREVER, bloom filter: none}]}
08/06/06 04:34:05 DEBUG client.HTable$ClientScanner: Advancing internal scanner to startKey
at 0003154574
....
{code}

We're getting all regions regardless.

> server side scanner doesn't honor stop row
> ------------------------------------------
>
>                 Key: HBASE-665
>                 URL: https://issues.apache.org/jira/browse/HBASE-665
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Michael Bieniosek
>             Fix For: 0.1.3, 0.2.0
>
>         Attachments: hbase-665.patch
>
>
> I have a large table.  If I create a scanner with a stop row near the beginning of the
table, the last hasNext call hangs for a while.  If I do the same with the stop row near the
end of the table, the last hasNext call is pretty quick.
> I suspect that the server side scanner isn't terminating early, and is actually scanning
through the whole table returning nothing.

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


Mime
View raw message