On Mon, Sep 28, 2015 at 12:19 PM, Moises Baly <[email protected]> wrote:
> Hi all: > > I would like to perform a range scan on a table, tweaking the definition > of what goes into a particular key range. One way I can think of is writing > a filter on the key, and that would work fine. But I think it would be slow > compared to a scan / seek custom iterator. How does the underlying login > works? Does Filter goes through all records, or since is sorted follows the > same underlying logic as a scan? Would a custom iterator perform better? > Yes, filter will read all data. Custom iterator that seeks may be faster. Are you aware of the following? https://issues.apache.org/jira/browse/ACCUMULO-3961 https://github.com/apache/accumulo/pull/42 > > Thank you for your time, > > Moises >
