Because I need to filter on (possibly) more than 1024 terms and using a
query to do it just wouldn't work.
Comron Sattari
On Wed, Mar 18, 2009 at 1:30 PM, David Smiley @MITRE.org
wrote:
>
> Although I'm not answering your question (others have), why are you even
> doing this at all with Solr wh
Although I'm not answering your question (others have), why are you even
doing this at all with Solr when you could take advantage of Solr's filter
queries (fq param)?
~ David Smiley
Comron Sattari-3 wrote:
>
> I've recently upgraded to Solr 1.3 using Lucene 2.4. One of the reasons I
> upgraded
I can try, for now I just decided to use Lucene's TermsFilter which does the
job perfectly. If I have some spare time I'll put together a unit test to
show the problem.
Thanks.
On Wed, Mar 18, 2009 at 12:23 PM, Grant Ingersoll wrote:
> Can you isolate this down to just a simple unit test?
>
>
>
Can you isolate this down to just a simple unit test?
On Mar 17, 2009, at 6:52 PM, Comron Sattari wrote:
I've recently upgraded to Solr 1.3 using Lucene 2.4. One of the
reasons I
upgraded was because of the nicer SearchComponent architecture that
let me
add a needed feature to the default re
I've recently upgraded to Solr 1.3 using Lucene 2.4. One of the reasons I
upgraded was because of the nicer SearchComponent architecture that let me
add a needed feature to the default request handler. Simply put, I needed to
filter a query based on some additional parameters. So I subclassed
Query
