[
https://issues.apache.org/jira/browse/SOLR-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471607
]
Hoss Man commented on SOLR-152:
-------------------------------
> I see your point on it not making sense... It is probably beter for the
> client to send a 'q' that > will match everything if that is what it is after.
i agree... but i don't think it makes sense to try and add some special syntax
to the "q" ... it probably makes more sense to add a new "matchall" param -- if
there is no q, and matchall=true then use a MatchAllDocs instead -- if neither
are set, throw an exception
(that way matchall can be set in the solrconfig as either a default or an
invariant)
> But it should throw a 400 exception!
no disagreement there ... improving the error messages in error input cases is
sometihng we need to do a lot of in Solr (most of hte focus in the past was on
good behavior for good input)
> 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.
