lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-4485) Consider making QParsers throw SyntaxError if field being searched is not indexed
Date Fri, 22 Feb 2013 14:18:15 GMT


Jan Høydahl commented on SOLR-4485:

-0 : This is a pretty big change in the user facing query syntax, and will cause tons of applications
out there to start crashing with exceptions. So at least it must be controlled by luceneMatchVersion
or a config-param so people can upgrade binaries but keep old behavior.

Also, (e)disMax must probably be changed to catch that exception from lucene-parser and do
some : escaping or something, since it's supposed to never crash on you :)
> Consider making QParsers throw SyntaxError if field being searched is not indexed
> ---------------------------------------------------------------------------------
>                 Key: SOLR-4485
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
> For historical reasons that i can't even really remember right now most query parsing
in solr don't seem to care if the fields they are asked to search are indexed.  Using hte
4x example schema (where the content field is stored but not indexed), all of these queries
return a 200 status code, and match 0 documents...
> {noformat}
> http://localhost:8983/solr/select?defType=lucene&q=ignored_xx:foo
> http://localhost:8983/solr/select?qf=ignored_xx&defType=edismax&q=foo
> http://localhost:8983/solr/select?qf=ignored_xx&defType=dismax&q=foo
> http://localhost:8983/solr/select?q={!field%20f=ignored_xx}foo
> http://localhost:8983/solr/select?q={!term%20f=ignored_xx}foo
> {noformat}
> I'm opening this issue to gather feedback on whether people think we should treat this
as a bug that should be fixed, or if folks think it's better to leave things as they stand.

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

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

View raw message