thanks Ted.
From: Ted Yu
Sent: Wednesday, May 3, 2017 3:32:12 PM
To: user@hbase.apache.org
Subject: Re: Is stop row included in the scan or not?
bq. stopRow - row to stop scanner before (exclusive)
On Wed, May 3, 2017 at 3:08 PM, jeff saremi wrote:
> by readin
bq. stopRow - row to stop scanner before (exclusive)
On Wed, May 3, 2017 at 3:08 PM, jeff saremi wrote:
> by reading the docs for 1.2 (https://hbase.apache.org/1.2/
> apidocs/org/apache/hadoop/hbase/client/Scan.html) i'm not able to tell if
> the stop row is returned in the results from a Scan o
by reading the docs for 1.2
(https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/client/Scan.html)
i'm not able to tell if the stop row is returned in the results from a Scan or
not. Could someone clear this up please? thanks
That's a good explanation, Kevin! It's also good to keep in mind that
the ResultScanner implementation is not reading data in parallel. You
have many servers to read data from, but you're only communicating with
one at a time.
Also, remember that HBase stores its data in sorted-order. The best
Lydia:
bq. including a prefix-filter and some column filter.
Are you expecting roughly same rate of filtering across the tables ?
Which hbase / hadoop release are you using ?
Cheers
On Wed, May 3, 2017 at 6:32 AM, Kevin O'Dell wrote:
> Hi Lydia,
>
> Welcome to the wonderful world of HBase!
Hi Lydia,
Welcome to the wonderful world of HBase! I don't think it is wrong that
you are seeing linear results from doing a scan. When doing a scan HBase
will collect X amount of rows to return to the client. X being the value of
your scan cache. If each round trip grabs 100 rows and takes 1 s
Hi,
I would like to know if my query times seem appropriate since I do not have a
lot experience with HBase.
I have three tables - stored in HDFS, on one machine:
table1: 5 million rows
table2: 15 million rows
table3: 90 million rows
I do a scan using the Java API incl