Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-14162

CAM-11779 was only added on db create scripts

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • 7.17.0-alpha1
    • engine
    • None

      Environment (Required on creation):

      Camunda 7.14

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

      https://jira.camunda.com/browse/CAM-11779 was fixed on camunda 7.14

      However, I see that the fix was only included on the DB create scripts and not on the DB update scripts:

      https://github.com/camunda/camunda-bpm-platform/commit/35b4deb3f785023e85873b994709f1c0fcbb49af

       

      We currently are on 7.11 and were planning an upgrade to 7.14 or higher to solve this issue in our side.

      Steps to reproduce (Required on creation):

      see above

      Observed Behavior (Required on creation):

      Table ACT_HI_ACTINST is still with incorrect ASSIGNEE size after upgrade to 7.14

      Expected behavior (Required on creation):

      The field should be 255.

      Root Cause (Required on prioritization):

      Solution Ideas (Optional):

      Hints (optional):

        This is the controller panel for Smart Panels app

            [CAM-14162] CAM-11779 was only added on db create scripts

            Nikola Koevski added a comment - - edited

            Hi desousru,

            The size of the ASSIGNEE column was updated only in the SQL create scripts intentionally. The reason was the following:

            Adjusting the size of the ASSIGNEE_ columns in the SQL upgrade scripts might impact the correct engine operation. As the ACT_HI_ACTINST table may contain a large amount of historical data, altering the column size on an existing database might take a significant amount of time since, during the migration, the column data might not be available for reads and writes in some databases (e.g. this is the case in Oracle).

            Furthermore, different databases have different recommendations on how to perform a migration correctly (e.g. see Oracle's guide, and it's not always easy to implement these recommendations in an SQL upgrade script easily.

            So, for migrations that impact tables that usually contain large amounts of data, we recommend that your DBA determine what is the best migration strategy.

            Therefore, I will close this ticket.

            Best,
            Nikola

            Nikola Koevski added a comment - - edited Hi desousru , The size of the ASSIGNEE column was updated only in the SQL create scripts intentionally. The reason was the following: Adjusting the size of the ASSIGNEE_ columns in the SQL upgrade scripts might impact the correct engine operation. As the ACT_HI_ACTINST table may contain a large amount of historical data, altering the column size on an existing database might take a significant amount of time since, during the migration, the column data might not be available for reads and writes in some databases (e.g. this is the case in Oracle). Furthermore, different databases have different recommendations on how to perform a migration correctly (e.g. see Oracle's guide , and it's not always easy to implement these recommendations in an SQL upgrade script easily. So, for migrations that impact tables that usually contain large amounts of data, we recommend that your DBA determine what is the best migration strategy. Therefore, I will close this ticket. Best, Nikola

            Rui Miguel Sousa Carvalho added a comment -

            Thanks for the explanation

            Rui Miguel Sousa Carvalho added a comment - Thanks for the explanation

              nikola.koevski Nikola Koevski
              desousru Rui Miguel Sousa Carvalho
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: