I feel very strongly that this code should be removed (or made an option that is disabled by DEFAULT). It should be left up to the individual installing the update of the repository to decide if further steps that will be taken. Large production Solr search indexes take a long time (entire days) to reconstruct on many of our repositories, they should not be completely destroyed and rebuilt from scratch without human input.
I feel very strongly that [this code|https://github.com/DSpace/DSpace/blame/master/dspace-api/src/main/java/org/dspace/storage/rdbms/DatabaseUtils.java#L1216-L1256] should be removed (or made an option that is disabled by DEFAULT). It should be left up to the individual installing the update of the repository to decide if further steps that will be taken. Large production Solr search indexes take a long time (entire days) to reconstruct on many of our repositories, they should not be completely destroyed and rebuilt from scratch without human input.
I would raise the priority of this and identify it as an important issue that should be corrected.
I've created a PR that wraps the automatic invocation of the ReindexerThread with a configurable property. Effectively allowing the user to configure the automatic triggering of the ReindexerThread
Draft 7.0 documentation updated. 6_x documentation should not be updated until 6.4 is released, and should note that this feature did not exist before that release.