[
https://issues.apache.org/jira/browse/SOLR-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471603
]
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...
http://www.nabble.com/DisMax-and-null-query-strings-tf2321023.html#a6457790
...at 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: https://issues.apache.org/jira/browse/SOLR-152
> 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:
> http://www.nabble.com/dismax-without-q%3D-tf3198431.html#a8880594
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
