If you usually get an error, such as: Unknown field... Or Missing field, and your schema.xml already contains those fields, make sure you disable the Schemaless mode in solrconfig.xml
Just head on to the Config Files Editor in your opensolr index control panel, and locate a snippet that looks like this:
class="ManagedIndexSchemaFactory"
According to the solr documentation, you can disable the ManagedIndexSchemaFactory as per the instructions below:
To disable dynamic schema REST APIs, use the following for: <schemaFactory class="ClassicIndexSchemaFactory"/>
Also do not forget to remove the entire snippet regarding the ManagedIndexSchemaFactory, so that you won't accidentally use both.
Common Reasons Your Schema Changes Are Not Applied
1. You Have Not Reloaded Your Index
After editing your schema.xml through the Opensolr Config Files Editor, you must reload your Opensolr Index for changes to take effect. Simply saving the file is not enough. Click the Reload button in your Opensolr Index control panel after every schema change.
2. Managed-Schema Is Overriding Your schema.xml
Solr can operate in two schema modes: classic mode (using schema.xml) and managed mode (using managed-schema). If your solrconfig.xml contains a ManagedIndexSchemaFactory definition, Solr ignores schema.xml entirely and uses managed-schema instead. This is the most common reason schema.xml changes appear to have no effect.
To check which mode is active, open your solrconfig.xml in the Config Files Editor and search for schemaFactory. If you see:
<schemaFactory class="ManagedIndexSchemaFactory">
...
</schemaFactory>Then your index is in managed mode. Replace it with the classic factory as described above to use schema.xml.
3. Typos in Field Names or Types
A common mistake is a mismatch between the field name in your schema.xml and the field name used when indexing documents. Field names are case-sensitive. For example, productName and productname are two different fields. Double-check your field definitions against the actual field names in your indexing requests.
4. Missing Field Types
If you reference a type in your field definition that does not exist in the schema, Solr will reject the configuration on reload. Make sure every type="..." attribute in your <field> definitions matches a <fieldType> defined elsewhere in the same schema file.
Step-by-Step Debugging Guide
- Check the Error Log: After reloading, click the Error Log button in your Opensolr control panel. If the schema has syntax errors or missing field types, the error messages will appear here.
- Verify the Active Schema: Use the Opensolr API or the Config Files Editor to confirm which schema file is currently active. If managed-schema exists and is being used, your schema.xml edits will not apply.
- Test with a Simple Field: Add a single new field to your schema, reload, and try indexing a document with that field. This isolates whether the issue is with the reload process or with a specific field definition.
- Compare Field Names: Make sure the field names in your indexing code (Drupal, WordPress, custom scripts) exactly match the field names in schema.xml, including case.
schema.xml vs managed-schema
Understanding the difference between these two approaches is important:
- schema.xml (Classic Mode): You manually edit the XML file to define fields and field types. Changes require a reload. This gives you full control and is recommended when you want a predictable, version-controlled schema.
- managed-schema (Managed Mode): Solr manages the schema file and allows changes through the Schema API (REST endpoints). This enables dynamic field creation without editing XML files but can lead to unexpected fields being added automatically.
On Opensolr, most users prefer classic schema.xml mode because it provides explicit control over the index structure. If you need to switch between modes, see our FAQ on moving from schema.xml to managed-schema.