Full reindex (index-discovery) is triggered whenever Flyway finds a new DB migration

Terry Brady [1:17 PM]
I just updated my instance from 5.6 to 5.7. It appears that a full discovery reindex was triggered. Does this happen automatically with any version upgrade? We had not anticipated the upgrade to take such a long time to complete.

Tim Donohue [1:18 PM]
@terrywbrady : Unfortunately it is triggered anytime a Flyway DB migration runs. In 5.7, there were new migrations (not to change the tables, but to add more resourcepolicies, and similar).

Terry Brady [1:19 PM]
I wish it was simply replacing items in solr rather than wiping the index clean... Our re-index takes 2-3 hours to run

Tim Donohue [1:20 PM]
I've never figured out a way to differentiate when it definitely needs to run, so we are currently erring on the side of "run more frequently than we likely need it to"

Terry Brady [1:20 PM]
It must have completed so quickly on my test instance that I did not notice.

Tim Donohue [1:21 PM]
I'd welcome improvements to the process...it's not "smart" right now... just gets triggered on Tomcat startup anytime Flyway actually finds & runs a new migration.