Task Schedule Log Migration

1. Version 

Note 1: for jars before May 20, 2019, the task schedule execution log is stored in fine_schedule_record of FineDB database; for jars on or after May 20, 2019, the task schedule execution log is stored in the fine_schedule_record of LogDB database.

Note 2: For the introduction of fine_schedule_record table fields, see: FineDB table structure

2. Problem description

After the jar package is upgraded to May 20, 2019, open the decision-making platform, and click Manage > Task schedule > run monitoring. When the task schedule is not running after the upgrade, the operation monitoring is blank. As shown in the figure below:

Note: the historical task schedule log will not be displayed in the platform, but the data still exists. To view the historical scheduling log, click Get Help in the upper left corner to jump to this article.

If users need to view the scheduling logs before May 20, 2019, what should they do?

3. Solution

Add new field to fine_conf_entity of FineDB database, and control the data source of the task schedule log.

Note: this idea only provides a way to query old logs. If jars after May 20, 2019 excecute the scheduled tasks, the log will still be stored in the fine_schedule_record table of LogDB database.

In table fine_conf_entityof FineDB database, add field ScheduleSettingConfig.swiftRecord, the value is false, restart the project, you can query the task scheduled log of the version before May 20, 2019.

Note 1: please refer to Built-in HSQL FineDB for the method of modifying the field value of the FineDB database table.

Note 2: the cleaning of the task schedule log is synchronized with the cleaning of the platform log. When the platform log is cleaned manually or automatically, the scheduled scheduling log will also be cleaned.