PR merged, marking as fixed.

https://github.com/OpenNMS/opennms/pull/1388

Here's a diff of the nms6584_two_triggers.txt and nms6584_post_upgrade.txt files. You can see that it's adding the sched_name column to many of the tables and doing some other schema migration (ie. is_volatile field) but the schedule data in qrtz_cron_triggers and qrtz_triggers stays the same.

I did some testing to make sure that the upgrade is working properly.

• I set up a foundation-2017 machine with a pristine set of Quartz tables

• A row is added to qrtz_job_details by Spring for the org.opennms.reporting.core.BatchReportJob on startup

• I took a dump of the Quartz tables (nms6584_pristine.txt)

• I scheduled two reports to execute every minute in the UI: this adds two rows to the qrtz_cron_triggers and qrtz_triggers tables

• I took a dump of the Quartz tables (nms6584_two_triggers.txt)

• I received a few report emails to make sure that the triggers were executing

• I stopped OpenNMS, upgraded to the branch RPMs, and ran the installer

• I took a dump of the Quartz tables (nms6584_post_upgrade.txt)

• I started up OpenNMS and made sure that the reports were being delivered with Quartz 2

Issue in the latest build:

Branch for this work: https://github.com/OpenNMS/opennms/tree/feature-upgrade-to-quartz-2.2