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 existence/absence of "q" parameter
Date Tue, 27 Mar 2012 00:43:26 GMT


Chris Male commented on SOLR-435:

bq. Sorry ... i was looking at my patched version – agreed it should throw ParseException

No worries.  I think we should ensure that all QParsers only use ParseException (I see that
ExtendedDisMaxQParser uses a c&p of the logic from DisMaxQParser).  I see that's what
your patch does.

Given te level of debate in this issue, and the differences in opinion on what the right /
wrong way to address this broader topic of query parsing validation i suggest we punt on this
for Solr 3.6 – I'd rather leave things the way they are then make a bad decision in a hurry

I agree but I also think we should commit the improved error message suggested by David so
that we avoid the unhelpful NPE.  Any broader changes will be in 4.0 so we don't have a backwards
compat problem.
> QParser must validate existence/absence of "q" parameter
> --------------------------------------------------------
>                 Key: SOLR-435
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Ryan McKinley
>            Assignee: David Smiley
>             Fix For: 3.6, 4.0
>         Attachments: SOLR-435.patch, 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