[
https://issues.apache.org/jira/browse/SOLR-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayya Sharipova updated SOLR-15403:
-----------------------------------
Security: (was: Public)
> Non-indexed DateRangeField throws SolrException
> -----------------------------------------------
>
> Key: SOLR-15403
> URL: https://issues.apache.org/jira/browse/SOLR-15403
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 8.6.3, 8.7, 8.8, 8.8.1, 8.8.2
> Environment: RHEL 7.9 (3.10.0-1160)/Windows (10.1909)
> OpenJDK 1.8.0.282
>
> Reporter: Tom Davidson
> Priority: Major
>
> Changes introduced by SOLR-14859 do not handle the scenario when the field is
> set to indexed=false. Forcing configurations to now index this field when it
> is not necessary.
> The problem appears to be in
> org.apache.solr.schema.AbstractSpatialPrefixTreeFieldType::checkSchemaField
> When indexed=false, field.indexOptions() returns IndexOptions.NONE. If
> condition does not handle this.
>
> I would also suggest lowering the logging level on some of the messages in
> setArgs(). Even when the options are not set in the schema definition, the
> defaults are causing the "warning" messages to be displayed. At best, these
> are informational, but, I don't find them particularly useful when the
> defaults or the specified values match the "required" settings.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
