Meghana -

Some important points about q/fq -

  * q is used for scoring.  fq is for filtering, no scoring.

  * fq and q are cached independently

You may want to combine the user entered terms (search term, title, and desc) 
in the q parameter.  It's complicated/advanced, but you can use nested queries 
to achieve a spread of different query contexts with different field 
configurations.  Check out Yonik's blog entry for inspiration: 
<http://www.lucidimagination.com/blog/2009/03/31/nested-queries-in-solr/>

        Erik



On Nov 23, 2011, at 00:59 , meghana wrote:

> Hi Erik , 
> 
> Actually right now we can say that almost is done in filtering and passing q
> as *:* , but we need to find out a better way if there is any. So according
> to pravesh , i m thinking of to pass user entered text in query and date and
> other fields in filter query? or as per you q=*:* is fast? 
> 
> I have below fields to search 
> Search Term  :  User Entered Text Field (passing it in q)
> Title : User Entered Text Field (passing it in fq)
> Desc : User Entered Text Field (passing it in fq)
> Appearing : User Entered Text Field (passing it in fq)
> Date Range : (passing it in fq)
> Time Zone : (EST , CST ,MST , PST) (passing it in fq)
> Category : (multiple choice) (passing it in fq)
> Market : (multiple choice) (passing it in fq)
> Affiliate Network : (multiple choice) (passing it in fq)
> 
> I really appreciate your view.
> Meghana
> Jeff Schmidt wrote
>> 
>> Hi Erik:
>> 
>> When using [e]dismax, does configuring q.alt=*:* and not specifying q
>> affect the performance/caching in any way?
>> 
>> As a side note, a while back I configured q.alt=*:*, and the application
>> (via SolrJ) still set q=*:* if no user input was provided (faceting). With
>> both of them set that way, I got zero results. (Solr 3.4.0)  Interesting.
>> 
>> Thanks,
>> 
>> Jeff
>> 
>> On Nov 22, 2011, at 7:06 AM, Erik Hatcher wrote:
>> 
>>> If all you're doing is filtering (browsing by facets perhaps), it's
>>> perfectly fine to have q=*:*.  MatchAllDocsQuery is fast (and would be
>>> cached anyway), so use *:* as appropriate without worries.
>>> 
>>>     Erik
>>> 
>>> 
>>> 
>>> On Nov 22, 2011, at 07:18 , pravesh wrote:
>>> 
>>>> Usually,
>>>> 
>>>> Use the 'q' parameter to search for the free text values entered by the
>>>> users (where you might want to parse the query and/or apply
>>>> boosting/phrase-sloppy, minimum match,tie etc )
>>>> 
>>>> Use the 'fq' to limit the searches to certain criterias like location,
>>>> date-ranges etc.
>>>> 
>>>> Also, avoid using the q=*:* as it implicitly translates to
>>>> matchalldocsquery
>>>> 
>>>> Regds
>>>> Pravesh
>>>> 
>>>> --
>>>> View this message in context:
>>>> http://lucene.472066.n3.nabble.com/how-to-make-effective-search-with-fq-and-q-params-tp3527217p3527535.html
>>>> Sent from the Solr - User mailing list archive at Nabble.com.
>>> 
>> 
>> 
>> 
>> --
>> Jeff Schmidt
>> 535 Consulting
>> jas@
>> http://www.535consulting.com
>> (650) 423-1068
>> 
> 
> 
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/how-to-make-effective-search-with-fq-and-q-params-tp3527217p3529876.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to