lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-435) QParser must validate existance/absense of "q" parameter
Date Sat, 24 Mar 2012 02:07:25 GMT


Chris Male commented on SOLR-435:

we definitely shouldn't modify QueryComponent ... the entire point of the issue is that QueryComponent
can't attempt to validate the q param, because it doesn't know if/when the defType QParser
requires it to exist – the individual QParsers all need to throw clear errors if they require
it and it's not specified, that's really the whole reason this issue was opened in the first

If the purpose of the QueryComponent is to be QParser agnostic and consequently unable to
know if the 'q' parameter is even relevant, shouldn't it be up to the QParser to retrieve
what it believes the query string to be from the request parameters?  Currently QueryComponent
assumes the 'q' parameter value is the query string, sets that as being the case in the ResponseBuilder
and passes it down to the QParser.
> QParser must validate existance/absense of "q" parameter
> --------------------------------------------------------
>                 Key: SOLR-435
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>             Fix For: 3.6, 4.0
>         Attachments: SOLR-435_q_defaults_to_all-docs.patch
> Each QParser should check if "q" exists or not.  For some it will be required others
> currently it throws a null pointer:
> {code}
> java.lang.NullPointerException
> 	at org.apache.solr.common.util.StrUtils.splitSmart(
> 	at
> 	at
> 	at org.apache.solr.handler.component.QueryComponent.prepare(
> 	at org.apache.solr.handler.SearchHandler.handleRequestBody(
>         ...
> {code}
> see:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message