Thanks Ted for the response, we have to look over the entire table for the
rowkeys so we can't set range for the scanner. It looks like we should
generally do multigets when we know the rowkeys and use the filterlist for
all other kind of filters.
Although I would check out the source and see if
Scan always comes with performance cost as its seek the table regardless
you are having filters, on the other hand Get is always give you the better
results, its actually based on your requirement Get can be helpful if you
the rowkey if you don't know you have to scan, yeah range based scan can
For the first code snippet, it seems start row / stop row can be specified
to narrow the range of scan.
For your last question:
bq. all the filters in the filterList are RowFilters ...
The filter list currently is not doing optimization even if all filters in
the list are RowFilters.
Cheers
Hi,
During our implementation for fetching multiple records from an HBase
table, we came across a discussion regarding the best way to get records
out.
The first implementation is something like:
FilterList filterList = new FilterList(Operator.MUST_PASS_ONE);
> for (String
