: Rather than rewriting the original query, add a filter query (fq param on the
: HTTP interface). I think in the API you'll be using rb.getFilters() and
: adding a filter to List returned.
that's what would probably make the most sense -- especially from a
filter caching standpoint.
: Running
)
Sent: Wednesday, April 28, 2010 7:32 PM
To: dev@lucene.apache.org; connectors-...@incubator.apache.org
Subject: RE: Solr query question
I tried the getFilters() approach. It turned out I also needed to create a
list and do setFilters() if getFilters() returns null, but that was easily
remedied
ednesday, April 28, 2010 6:40 PM
To: dev@lucene.apache.org; connectors-...@incubator.apache.org
Subject: RE: Solr query question
Adding to the getFilters() list seems reasonable - although, to be fair, my
code does seem to work as intended when the component is added "last". I'll
ot [ear...@gmail.com]
Sent: Wednesday, April 28, 2010 6:52 PM
To: dev@lucene.apache.org
Subject: Re: Solr query question
The best way to match documents that have no values for a specific
field, is to have a special term in that (or another) field, that you
add to the index when, well, a document ha
om: ext Erik Hatcher [erik.hatc...@gmail.com]
> Sent: Wednesday, April 28, 2010 5:54 PM
> To: connectors-...@incubator.apache.org
> Cc: dev@lucene.apache.org
> Subject: Re: Solr query question
>
> Rather than rewriting the original query, add a filter query (fq param
> on the HTTP interface). I t
ance, for what it's worth...)
Karl
From: ext Erik Hatcher [erik.hatc...@gmail.com]
Sent: Wednesday, April 28, 2010 5:54 PM
To: connectors-...@incubator.apache.org
Cc: dev@lucene.apache.org
Subject: Re: Solr query question
Rather than rewriting the original query, add a filt
Rather than rewriting the original query, add a filter query (fq param
on the HTTP interface). I think in the API you'll be using
rb.getFilters() and adding a filter to List returned.
Running your component last won't work (will it?), as it needs to be
run before the "query" component to t
Turns out that, for the standard requestHandler, running this SearchComponent
first causes its rewritten query to be lost. Running last fixed the problem.
(I'd *love* to know why that would be necessary.)
But I'd still like comment as to whether the WildcardFilter construct is
expected to be
