[
https://issues.apache.org/jira/browse/SOLR-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200933#comment-13200933
]
Mike Sokolov commented on SOLR-1758:
------------------------------------
Yes - the schema will have to evolve as the config files evolve, so there will
be a need for a new version, probably with each release.
I think matching using LuceneMatchVersion makes a lot of sense. For versions
that are old enough (eg a different major release), the validator could still
run, but produce warnings only. Or else it could simply produce a message
saying: "warning; stale config version, not validating" or something to that
effect. I'm not clear on how reasonable it is to maintain an old config
version: isn't this the kind of thing that users will *want* to be prompted to
revisit?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
