"Schema modified" warning

The status report check loads the current config-set in use from the Solr server it compares it to the current one that would be generated by the module. If it differs, you'll get this warning. (Differences in langauages or module versions lead to other warnings.)

You can get rid of the warning by generating and deploying a new config-set.

To se the difference you can also download the config-set from Solr and compare it to a newly generated one (using a recursive diff on the command line.)

Thanks

Automatically closed - issue fixed for 2 weeks with no activity.

Just reporting back, in case anyone else is experiencing this issue:

The status check fails in two odd cases.

Case 1: Where the exported config set and the installed config set are identical except for the order of some of the properties on the XML nodes. The value of the properties and the properties themselves are identical, just in a different order. So functionally, the XML is identical but the status report will still trigger a warning, which is unwarranted in this case.

Case 2: In my QA environment, I have configured the solr server to symlink /var/solr/data/mycore/conf to a mounted solr-conf directory. The contents of that mounted solr-conf directory consists exactly and exclusively of the config-set I exported from that very server before rebuilding it. So I downloaded the config-set from the QA server. I expanded the zip file into my solr-conf directory, rebuilt my QA solr server, and I still get the status report warning. If I shell into my QA solr server and compare the files in /var/solr/data/mycore/conf to the files I get when downloading the zip, they are identical.

I can only conclude that the comparison in this function is a little off and I advise people to ignore the warning if they have aleady made a good faith effort to resolve it with a new config.zip retrieval.