: Hello - I stumbled upon a odd bug, or what appears to be a bug, today. : I have been using my own custom version numbers for my schema and tried : to change the version number from 0.8 to 0.8.1 which rendered solr : useless yielding a schema parsing error. I then tried to change it to : 0.8-1 with the same results.
the "version" attribute of a schema has a very specific meaning relating to how the schema.xml file will be parsed. There is a note about this in the example schema.xml... http://svn.apache.org/viewvc/lucene/solr/trunk/example/solr/conf/schema.xml?view=markup <schema name="example" version="1.1"> <!-- attribute "name" is the name of this schema and is only used for display purposes. Applications should change this to reflect the nature of the search collection. version="1.1" is Solr's version number for the schema syntax and semantics. It should not normally be changed by applications. 1.0: multiValued attribute did not exist, all fields are multiValued by nature 1.1: multiValued attribute introduced, false by default --> ...that said, Solr should probably warn you (and function as if the default version is specified) if an unrecognized version number is found. feel free to open a bug to do that. -Hoss
