Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-33336

duplicate QRTZ_JOB IS_STATEFUL select columns sakai_11_mysql_conversion.sql

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Non-Issue
    • Affects Version/s: 11.4, 12.0
    • Fix Version/s: None
    • Component/s: Reference
    • Labels:
      None
    • Test Plan:
      Hide

      Please add a Test Plan here.

      Show
      Please add a Test Plan here.

      Description

      sakai_11_mysql_conversion.sql

      line 604

      INSERT INTO QRTZ_JOB_DETAILS_NEW (SCHED_NAME, JOB_NAME, JOB_GROUP, DESCRIPTION, JOB_CLASS_NAME, IS_DURABLE, IS_NONCONCURRENT, IS_UPDATE_DATA, REQUESTS_RECOVERY, JOB_DATA) SELECT 'QUARTZSCHEDULER', JOB_NAME, JOB_GROUP, DESCRIPTION, JOB_CLASS_NAME, IS_DURABLE, IS_STATEFUL, IS_STATEFUL, REQUESTS_RECOVERY, JOB_DATA FROM QRTZ_JOB_DETAILS;

      which is inserting existing data into a temp. table in order to replace QRTZ_JOB_DETAILS. In the nested select, there are duplicate IS_STATEFUL select columns. One of them should probably be IS_VOLATILE because the original QRTZ_JOB_DETAILS table looks like

      mysql> desc QRTZ_JOB_DETAILS;
      +-------------------+--------------+------+-----+---------+-------+
      | Field             | Type         | Null | Key | Default | Extra |
      +-------------------+--------------+------+-----+---------+-------+
      | JOB_NAME          | varchar(80)  | NO   | PRI | NULL    |       |
      | JOB_GROUP         | varchar(80)  | NO   | PRI | NULL    |       |
      | DESCRIPTION       | varchar(120) | YES  |     | NULL    |       |
      | JOB_CLASS_NAME    | varchar(128) | NO   |     | NULL    |       |
      | IS_DURABLE        | varchar(1)   | NO   |     | NULL    |       |
      | IS_VOLATILE       | varchar(1)   | NO   |     | NULL    |       |
      | IS_STATEFUL       | varchar(1)   | NO   |     | NULL    |       |
      | REQUESTS_RECOVERY | varchar(1)   | NO   |     | NULL    |       |
      | JOB_DATA          | blob         | YES  |     | NULL    |       |
      +-------------------+--------------+------+-----+---------+-------+
      9 rows in set (0.00 sec)
      

      but i'm not certain how the old columns: IS_VOLATILE, IS_STATEFUL should map to the new columms: IS_NONCONCURRENT, IS_UPDATE_DATA. Just going by the order that they appear, that's how they could map, but I don't know?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jonespm Matthew Jones
                Reporter:
                austinUH Austin
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Git Source Code