On Thu, Feb 21, 2008 at 1:20 PM, Owens, Martin
[EMAIL PROTECTED] wrote:
We have a requirement for being able to switch on and off certain filters
for different searches.
Can the client send in which filters should be turned on and off, but
leave the definition of the filters in
Can the client send in which filters should be turned on and off, but
leave the definition of the filters in solrconfig.xml?
The client must set the property, how solr deals with that is how I want it to
work.
If so, you can get this effect with the new query parser plugin
framework. Part
On Thu, Feb 21, 2008 at 1:49 PM, Owens, Martin
[EMAIL PROTECTED] wrote:
So you could add something like this to your query
fq=!val=$filter1fq=!val=$filter3)
and have the various filters be a default defined in a handler in
solrconfig.xml
How does this work? I'm still confused from
This feature was first committed 10/22/07
Great! should be there then.
Now put filter1 as a default in your handler (same as any other
default), and the client can turn on and off filter1 without knowing
what exactly it is.
OK so I have to add a new search hander into solrconfig.xml with
On Thu, Feb 21, 2008 at 2:17 PM, Owens, Martin
[EMAIL PROTECTED] wrote:
Now put filter1 as a default in your handler (same as any other
default), and the client can turn on and off filter1 without knowing
what exactly it is.
OK so I have to add a new search hander into solrconfig.xml
OK, talk of different fields threw me.
To enable a client to turn on/off a specific filter without knowing
what that filter is,
add the following parameter to the query string when you want to turn
the filter on:
fq=!v=$filter1
Then add a default for the filter1 param in lucene query syntax
What field??? or what filter?
I'm not really sure I still understand what you are trying to accomplish.
Perhaps if you have some explicit examples of what types of things
clients would send in as query parameters to Solr, and what types of
lucene queries you actually want to be generated.
