Comment #2 on 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
That's correct. I missed that.
But still the possibility to see the deleted secondary key from the
secondary index in reality could be very low.
We need to profile the pros and cons of using bloomfilter in this situation.
Probably, pin/unpin will be the major cost if the page is not in the
buffercache already plus the overhead of going through buffer cache's
critical section. Other than that, computing hash value will be the next
major cost.
--
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
