In theory, a returned primary key could be deleted because secondary index search does not lock anything... Is the overhead mostly from pin/un-pin BF pages?
Best, Yingyi On Mon, Aug 10, 2015 at 1:03 AM, <[email protected]> wrote: > Status: Accepted > Owner: [email protected] > Labels: Type-Enhancement Priority-Medium > > New issue 925 by [email protected]: Bloomfilter search preceded by > primary index lookup after secondary index search is nothing but overhead > since all primary keys returned from secondary indexes are all valid and > exist. > https://code.google.com/p/asterixdb/issues/detail?id=925 > > Bloomfilter search preceded by primary index lookup after secondary index > search is nothing but overhead since all primary keys returned from > secondary indexes are all valid and exist. > > -- > You received this message because this project is configured to send all > issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings >
