[
https://issues.apache.org/jira/browse/SOLR-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471815
]
Hoss Man commented on SOLR-152:
-------------------------------
>> at a broader level: annotating the "q" doesn't really address the issue of
>> letting the "solrconfig owner" specify what >> the behavior should be: an
>> extra param can be baked into the config, but a prefix on a user query can
>> not.
to clarify, the default in the solrconfig could of course be <str
name="q"><!lucene>*:*</str> ... but if the client has to prepend
<!dismax> on the front of user input anyway, it can't do it blindly (or it
might send an "empty" query of "<!dismax>" and defeat the point of the default)
with an extra param, the lcient doesn't even have to know anything special is
happening when hte user provides an epty string -- it doesn't even have to
check to see if hte user has provided an empty string
> 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, 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.
