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 take effect.
Re: WildcardFilter - I think you want TermRangeQuery there instead.
Erik
On Apr 28, 2010, at 5:35 PM, <karl.wri...@nokia.com> wrote:
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 efficient in this context, or not. ;-)
Karl
________________________________________
From: Wright Karl (Nokia-S/Cambridge)
Sent: Wednesday, April 28, 2010 2:57 PM
To: connectors-...@incubator.apache.org
Subject: Solr query question
Hi Solr-knowledgeable folks,
The LCF Solr SearchComponent plugin I'm developing doesn't quite
work. The query I'm trying to do is:
-(allow_token_document:*) and -(deny_token_document:*) and <the
user's search>
The result I'm seeing is that everything in the user's search
matches, unlike what I see in the admin UI, where the above query
works perfectly.
The code I'm using to do the negative wildcard searches is as follows:
public void prepare(ResponseBuilder rb) throws IOException
{
BooleanFilter bf = new BooleanFilter();
// No authenticated user name; only return 'public' documents
(those with no security tokens at all)
// That query is:
// (fieldAllowShare is empty AND fieldDenyShare is empty AND
fieldAllowDocument is empty AND fieldDenyDocument is empty)
// We're trying to map to: -(fieldAllowShare:*) , which should
be pretty efficient in Solr because it is negated. If this turns
out not to be so, then we should
// have the SolrConnector inject a special token into these
fields when they otherwise would be empty, and we can trivially
match on that token.
bf.add(new FilterClause(new WildcardFilter(new
Term(fieldAllowDocument,"*")),BooleanClause.Occur.MUST_NOT));
bf.add(new FilterClause(new WildcardFilter(new
Term(fieldDenyDocument,"*")),BooleanClause.Occur.MUST_NOT));
// Concatenate with the user's original query.
FilteredQuery query = new FilteredQuery(rb.getQuery(),bf);
rb.setQuery(query);
}
Any hints welcome!
Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
