Comment #1 on issue 924 by [email protected]: Secondary btree index should
not have a bloomfilter on it since the filter is not used for range search
which is always the case for secondary index search
https://code.google.com/p/asterixdb/issues/detail?id=924
Then I would challenge the approach of "always doing a range search on a
secondary index." What if we have a condition "price = 20" where there is
a secondary B-tree on "price"? Clearly a bloom filter can help this
predicate. Do we miss an opportunity of optimization here?
--
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