asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yingyi Bu <buyin...@gmail.com>
Subject Re: Issue 925 in asterixdb: 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.
Date Mon, 10 Aug 2015 08:22:25 GMT
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, <asterixdb@googlecode.com> wrote:

> Status: Accepted
> Owner: kiss...@gmail.com
> Labels: Type-Enhancement Priority-Medium
>
> New issue 925 by kiss...@gmail.com: 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message