Uploaded image for project: 'Ranger'
  1. Ranger
  2. RANGER-2295

Set specific Ranger version in patches status entry table

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0, 1.1.0, 1.2.0
    • Fix Version/s: 1.0.1, 2.0.0, 1.1.1, 1.2.1
    • Component/s: Ranger
    • Labels:
      None

      Description

      DB setup script looks for a specific version (Ranger 2.0.0-SNAPSHOT) to decide if patches need to be applied:

      select version from x_db_version_h where version = 'DB_PATCHES' and inst_by = 'Ranger 2.0.0-SNAPSHOT' and active = 'Y';
      select version from x_db_version_h where version = 'JAVA_PATCHES' and inst_by = 'Ranger 2.0.0-SNAPSHOT' and active = 'Y';
      

      However, the optimized schema creation script comes with a generic version (Ranger 1.0.0):

      INSERT INTO x_db_version_h (version,inst_at,inst_by,updated_at,updated_by,active) VALUES ('DB_PATCHES',CURRENT_TIMESTAMP,'Ranger 1.0.0',CURRENT_TIMESTAMP,'localhost','Y');
      INSERT INTO x_db_version_h (version,inst_at,inst_by,updated_at,updated_by,active) VALUES ('JAVA_PATCHES',CURRENT_TIMESTAMP,'Ranger 1.0.0',CURRENT_TIMESTAMP,'localhost','Y');
      

      The result is that a separate check is executed for each patch, which takes time. It will be good if the status entries have the exact ranger version rather a base version.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pradeep Pradeep Agrawal
                Reporter:
                pradeep Pradeep Agrawal
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: