Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-19223

Implement accumulation of schema updates in CatalogService

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

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0
    • None

    Description

      CatalogService implementation should hold the historical information about schema updates. This means that:

      1. It needs to load the known history of schema updates on node start
      2. It should subsribe to new schema updates

      Attachments

        Issue Links

        is fixed by

        Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. IGNITE-19502 Separate component to keep database schema and manage changes in it

        • Major - Major loss of function.
        • Resolved

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

          People

            Unassigned Unassigned
            rpuch Roman Puchkovskiy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment