Job scheduler migration job is not available in Sakai 12
GENERAL
TESTING
GENERAL
TESTING
Description
It seems like the migration job described in SAK-31819 was neither documented nor available as a job that can be selected.
Therefore any delayed notifications created prior to the upgrade to Sakai 12 appear to be abandoned in the old scheduler_delayed_invocation table.
We should have this available similar to the assignments job. I feel like the plan was below, however step 2 seems incomplete:
1) Upgrade to 12 2) Run the Scheduler Migration job (Assignment job has to run anyway so this isn't a big deal) 3) Drop the scheduler_delayed_invocation table (and probably old assignment tables) in Sakai 13. . . Not sure since some schools may jump from 11 to 13 and skip 12, then we don't want to just drop them.
Yeah, that sounds probable that something else between the original patch and release removed it. Unfortunately it wasn't documented that it was something we needed to do so we forgot to test it.
Matthew Buckett May 8, 2018 at 5:15 AM
Could this be related to SAK-39652?
Derek Ramsey May 4, 2018 at 1:55 PM
Tested on Sakai nightly 13. Verified in the logs that the job executed.
It seems like the migration job described in SAK-31819 was neither documented nor available as a job that can be selected.
Therefore any delayed notifications created prior to the upgrade to Sakai 12 appear to be abandoned in the old scheduler_delayed_invocation table.
We should have this available similar to the assignments job. I feel like the plan was below, however step 2 seems incomplete:
1) Upgrade to 12
2) Run the Scheduler Migration job (Assignment job has to run anyway so this isn't a big deal)
3) Drop the scheduler_delayed_invocation table (and probably old assignment tables) in Sakai 13. . . Not sure since some schools may jump from 11 to 13 and skip 12, then we don't want to just drop them.