Exact. When you specify start row, you jump directly to the right place. And you stop at end row. Also, if you add a filter to that, you will skip (server side) some other rows.
JM 2014-05-12 23:17 GMT-04:00 mu yu <[email protected]>: > Hi JM, > Thanks for your reply . > Ok,that's mean when filter or start row and stop row are used ,the scan > would skip the other rows. > Thank you so much. > > > On Tue, May 13, 2014 at 2:15 AM, Jean-Marc Spaggiari < > [email protected]> wrote: > > > Hi Mu, > > > > For a scan you can give start row and stop row. If you do so, it's only a > > partial scan. Also, if you add filters, rows are skipped on the server > > side. > > > > So you need to think your key to match your access pattern to avoid huge > > scans. > > > > JM > > > > > > 2014-05-07 5:06 GMT-04:00 mu yu <[email protected]>: > > > > > Hi > > > We deployed a hbase-hadoop cluster for log storage .It's known hbase > > has > > > no index , i wanna know all the scan including the hbase filter scan > are > > > full table scan ,and there's no other scans ? > > > For example if implement a rowkey scan by rowkey filter , and hbase > > > would execute a full table scan . > > > > > > Any reply are appreciate.Thanks in advance. > > > > > >
