ier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Sandeep Khanzode [mailto:sandeep_khanz...@yahoo.com.INVALID]
> Sent: Tuesday, August 12, 2014 8:53 AM
> To: Lucene Users
> Subject: BitSet in Filters
>
> Hi,
Hi Erick,
I have mentioned everything that is relevant, I believe :).
However, just to give more background: Assume documents of the order of more
than 300 million, and multiple concurrent users running search. I may front
Lucene with ElasticSearch, and ES basically calls Lucene TermFilters. My
bq: Unless, I can cache these filters in memory, the cost of constructing
this filter at run time per query is not practical
Why do you say that? Do you have evidence? Because lots and lots of Solr
installations do exactly this and they run fine.
So I suspect there's something you're not telling
Hi,
The current usage of BitSets in filters in Lucene is limited to applying only
on docIDs i.e. I can only construct a filter out of a BitSet if I have the
DocumentIDs handy.
However, with every update/delete i.e. CRUD modification, these will change,
and I have to again redo the whole proce
