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

Improve Ranger database schema import logic and make it more robust

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.5.0, 0.6.0, 0.7.0, 0.6.1
    • 0.7.0, 0.6.2
    • Ranger
    • None

    Description

      Problem Statement: Ranger installation process should handle concurrent import of DB schema as concurrent execution of db schema files can lead to an inconsistent state of data and application.

      Proposed Solution : Before importing db schema file; installation process will insert status in x_db_version_h table with active='N' value. If schema will get created/imported successfully then status of the schema creation flag will be set to 'Y' else status row from x_db_version_h will be deleted. If the Ranger DB schema is being imported then the active column will have the value 'N' and no other process will be allowed to import that file.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            pradeep Pradeep Agrawal
            pradeep Pradeep Agrawal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment