On Nov 22, 2011, at 09:55 , Jeff Schmidt wrote:
> When using [e]dismax, does configuring q.alt=*:* and not specifying q affect
> the performance/caching in any way?
No different than using q=*:* with the "lucene" query parser.
MatchAllDocsQuery is possibly the fastest query out there! (it simply matches
documents in index order, all scores are 1.0)
> 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.
Ouch. Really? I don't see in the code (looking at my trunk checkout) where
there's any *:* used in the SolrJ library. Can you provide some details on how
you used SolrJ? It'd be good to track this down as that seems like a bug to me.
Erik
>
> 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
> j...@535consulting.com
> http://www.535consulting.com
> (650) 423-1068
>
>
>
>
>
>
>
>
>
