lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Sokolov (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-1758) schema definition for configuration files (validation, XSD)
Date Tue, 03 Apr 2012 03:13:01 GMT


Mike Sokolov commented on SOLR-1758:

I updated the patch so it works with the new file layout in trunk (all solr test now pass
for me), put the schemas on the classpath, added declarations to the eclipse (tested) and
IDEA (untested) configs, added a version-check so we only validate config marked as LUCENE_40
or LUCENE_CURRENT, and added a couple of new tests related to these changes.  I don't have
the knowledge to create schemas for all the 3.x versions that would be meaningfully different.
 A possible approach there could be simply to use the same schema and make the version check
looser.  The only change I made (since a year ago) to the config.rnc was to allow a few new
options, so I think that would be reasonable given the level of strictness (not very) we can
impose here.  As long as future schema file changes are additive, you might actually not need
to create new versions?

I haven't tested WAR packaging - will the ant rules just pick up files in solr/core/src/resources?

Please note - there is not a separate schema for solrconfig.xml and schema.xml; one schema
applies to both (and also to a few other random config file types).
> schema definition for configuration files (validation, XSD)
> -----------------------------------------------------------
>                 Key: SOLR-1758
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Jorg Heymans
>              Labels: configuration, schema.xml, solrconfig.xml, validation, xsd
>             Fix For: 4.0
>         Attachments: config-validation-20110523.patch, config-validation-20120402.patch
> It is too easy to make configuration errors in Solr without getting warnings. We should
explore ways of validation configurations. See mailing list discussion at

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


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

View raw message