lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-435) QParser must validate existence/absence of "q" parameter
Date Tue, 27 Mar 2012 16:32:28 GMT


Hoss Man commented on SOLR-435:

bq. Why not simply apply the SOLR-2001 patch for consistent behavior?

good question ... if you're cool with that then it seems okay to me (although off the top
of my head i think when i was looking at trunk one of those 4 "main" parsers still needed
"fixed" to return null).

in general my suggestion for 3.6 was largely based on the fact that there was still active
discussion about what the best long term behavior was, which might contradict what was discussed
in SOLR-2001, so better to play it safe and just clean up the error reporting: "I'd rather
leave things the way they are then make a bad decision in a hurry"

if you want to backport SOLR-2001 and sanity check that lucene/dismax/edismax/lucenePlusSort
all return null on null/blank query strings i'm +1 to that (that seems consistent with what
ryan/male/me were advocating here, so as long as your on board i think we're good)

> 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_3x_consistent_errors.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