Seems like a good idea. Could you open a JIRA issue for this task? Mark
Sent from my iPhone On Dec 10, 2012, at 6:44 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > Hello, > > I lost good several hours on this, so wanted to check whether this is > fixable. > > In the (binary) distribution of Solr 4, there is a large number of > schema.xml files. But their version numbers are all over the place. Some > are 1.1, others 1.2 and - I think - only one on 1.5. I am talking about: > <schema name="rss" version="1.1"> > > Given that this tiny number strongly affects defaults and I think in some > cases flips them, getting wrong (e.g. by coping DIH example instead of the > main one) could really get a newbie confused. > > Would it be possible to make them all use a latest version? What would the > testing process be? > > Would it be sufficient to index once with existing value, change the value, > build second index and do binary file compare? Or is Lucene not as > predictable as that (e.g. due to internal timestamps)? > > Or is there a way to export a normative encoding of the field definition > and compare what changed and which fields/properties need to be set > explicitly after version change? > > Regards, > Alex. > > Personal blog: http://blog.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all at > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book)
