You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2026/09/27 02:46:00 UTC
[jira] [Resolved] (SOLR-18175) A FieldExistsQuery IllegalStateException should result in HTTP 400 not 500 error
[ https://issues.apache.org/jira/browse/SOLR-18175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley resolved SOLR-18175.
---------------------------------
Fix Version/s: 10.1
Resolution: Fixed
> A FieldExistsQuery IllegalStateException should result in HTTP 400 not 500 error
> --------------------------------------------------------------------------------
>
> Key: SOLR-18175
> URL: https://issues.apache.org/jira/browse/SOLR-18175
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Minor
> Labels: newdev, pull-request-available
> Fix For: 10.1
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> If you issue an existence query {{field:*}} yet that field does not support Lucene's {{FieldExistsQuery}}, FEQ.rewrite will throw IllegalStateException:
> bq. FieldExistsQuery requires that the field indexes doc values, norms or vectors, but field 'foo' exists and indexes neither of these data structures
> Solr ultimately returns a HTTP 500, which is not what we want. We want HTTP 400. Note that I discovered this via a {{facet.query}} and have yet to check if it were to happen simply in a {{q}}. The change likely involves modifying Solr {{FieldType.getExistenceQuery}} to throw an exception with the 400 code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org