Martin,

One option is:

q=name:iPod&fq=brand:Apple


That way, when you want to search for some other Apple product, Solr will reuse 
the Apple filter if you again use fq=brand:Apple with the new q=name:foo query.

Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch



----- Original Message ----
> From: Martin Davidsson <martin.davids...@gmail.com>
> To: solr-user@lucene.apache.org
> Sent: Wednesday, June 3, 2009 4:15:55 PM
> Subject: Re: fq vs. q
> 
> On Wed, Jun 3, 2009 at 1:53 AM, Marc Sturlese wrote:
> 
> >
> > It's definitely not proper documentation but maybe can give you a hand:
> >
> > 
> http://www.derivante.com/2009/04/27/100x-increase-in-solr-performance-and-throughput/
> >
> >
> > Martin Davidsson-2 wrote:
> > >
> > > I've tried to read up on how to decide, when writing a query, what
> > > criteria goes in the q parameter and what goes in the fq parameter, to
> > > achieve optimal performance. Is there some documentation that
> > > describes how each field is treated internally, or even better, some
> > > kind of rule of thumb to help me decide how to split things up when
> > > querying against one or more fields. In most cases, I'm looking for
> > > exact matches but sometimes an occasional wildcard query shows up too.
> > > Thank you!
> > >
> > > -- Martin
> > >
> > >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/fq-vs.-q-tp23845282p23847845.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
> >
> 
> Thanks, I'd seen that article too. I totally agree that it's worth
> understanding how things are treated under the hood. That's the kind of
> literature I'm looking for I guess. Given that article, I wasn't sure what
> the query would look like if I need to query against multiple fields. Let's
> say I have a "name" field and a "brand" field and I want to find the Apple
> iPod. Using only the 'q' param the query would look like
> select?q=brand:Apple AND name:iPod
> 
> Is there a better query format that utilizes the fq field? Thanks again
> 
> -- Martin

Reply via email to