On #dspace mhwood, hpottinger and I discussed
DS-2297 yesterday. DS-2297 fixes the problem that we might have an automatically updated database schema with an old lucene/solr index. While the database is checked and upgraded (if necessary) whenever the DSpace kernel starts, lucene/solr indexes are checked and updated during deployment, using ant.
This may lead to problems during deployment, depending on the exact deployment process. E.g. if the build and production server are seperate machines and packages (tar-balls, rpms, debs) are build for deployment. Or if ant doesn't run with the same user as tomcat, maybe by using group filesystem permissions... I think there might be many other ways of deploying DSpace and it would be good to move any upgrade (database, indexes) from the deployment to the startup process.
It would be good if we could update the solr/lucene indexes during startup of dspace-solr instead of running as ant target. Then the database and the indexes would be checked and updated during startup and we wouldn't have an unbalance between database and index upgrades.