[
https://issues.apache.org/jira/browse/SOLR-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199951#comment-13199951
]
Jan Høydahl commented on SOLR-1758:
-----------------------------------
In light of SOLR-3093 and SOLR-1052, have you thought about how to handle
validation of older versions of config/schema? A Solr1.3 user may upgrade to
Solr4.0 and simply point it to the old configuration. Some syntax and
parameters are deprecated and removed between versions.
Perhaps a solution is to NOT try to validate older versions of configs, and
when we go from 4.0 to 4.1, there will be a new config_41.xsd in addition to
config_40.xsd, and your code will select xsd based on LuceneMatchVersion?
> schema definition for configuration files (validation, XSD)
> -----------------------------------------------------------
>
> Key: SOLR-1758
> URL: https://issues.apache.org/jira/browse/SOLR-1758
> 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
>
>
> 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 http://search-lucene.com/m/h6xKf1EShE6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
