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 q
Jeff,
Just to clarify - with edismax, q=*:* is fine and matches all documents. With
dismax (and also edismax), q.alt with no q is needed to match all documents.
Erik
On Nov 23, 2011, at 08:20 , Jeff Schmidt wrote:
> Thanks, Erik. I'm moving on to edismax, and will set q.alt=*:* an
Thanks, Erik. I'm moving on to edismax, and will set q.alt=*:* and not specify
q if no user provided terms.
Take it easy,
Jeff
On Nov 22, 2011, at 11:53 AM, Erik Hatcher wrote:
> I think you're using dismax, not edismax. edismax will take q=*:* just fine
> as it handles all Lucene syntax que
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 think you're using dismax, not edismax. edismax will take q=*:* just fine as
it handles all Lucene syntax queries also. dismax does not.
So, if you're using dismax and there is no actual query (but you want to get
facets), you set q.alt=*:* and omit q - that's entirely by design.
If there's
Hi Erik:
It's not in the SolrJ library, but rather my use of it:
In my application code:
protected static final String SOLR_ALL_DOCS_QUERY = "*:*";
/*
* If no search terms provided, then return all neighbors.
* Results are to be returned in neighbor symbol alphabetical order.
*/
if (search
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 sim
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 wa
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
Thanks Pravesh for your reply..
I definitely try this.. i hope it will improve solr response time.
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, minim
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 t
11 matches
Mail list logo
