lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (SOLR-152) Dismax should not require 'q'
Date Fri, 09 Feb 2007 07:17:05 GMT


Hoss Man commented on SOLR-152:

past discussion (along with my concerns about what it means semanticly to not have a "q")
are in this thread... the time what was discussed was having the absence of a "q" param would result in the
"main" query being a MatchAllDocs -- the intent being that having a "q" tells dismax what
you want your superset to be, and not having a "q" tells it to default to everything.  (since
there is no easy syntax for telling dismax to match all like there is in the standard handler)

This patch takes a different approach: defaulting to nothing (so no matter how many FQs you
add, you still get nothing) ... that doesn't really seem that usefull to me -- sure it eliminates
the exception, but it doesn't gain the user functionality they didn't have before.

(this behavior isn't obvious when looking at the test in the patch, because the test config
has a default "bf" which is being used even when the "q" isn't)

> Dismax should not require 'q'
> -----------------------------
>                 Key: SOLR-152
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>            Reporter: Ryan McKinley
>            Priority: Trivial
>         Attachments: SOLR-152-DismaxNoQ.patch
> using fq=xxx should be sufficient to make a valid query
> see:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message