Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
8.11.1
-
None
-
None
-
Linux smeagol 5.13.0-25-generic #26~20.04.1-Ubuntu SMP Fri Jan 7 16:27:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)Linux smeagol 5.13.0-25-generic #26~20.04.1-Ubuntu SMP Fri Jan 7 16:27:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux openjdk version "11.0.13" 2021-10-19 OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu-0ubuntu1.20.04) OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)
Description
If a DateRangeField type is added to the schema, the schema will fail to initialize if any field referencing that type has indexed="false" as part of its definition.
So adding this to a schema will fail:
<fieldType name="rdate" class="solr.DateRangeField" sortMissingLast="true"/> <field name="date" type="rdate" indexed="false" stored="true"/>
With this message and a big stacktrace:
Caused by: org.apache.solr.common.SolrException: date of type DateRangeField is incompatible with omitNorms=false; hardcoded behavior is omitNorms=true. Remove specification in schema
If indexed is changed to "true" then the core will load.