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

Schema synchronization feature and Catalog feature integration

    XMLWordPrintableJSON

Details

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

    Description

      Metadata synchronization should be used, implemented (most likely) on top of "transactions in the past", defined in the transactions IEP (see "Lock-free RW Transactions" in https://cwiki.apache.org/confluence/display/IGNITE/IEP-91:+Transaction+protocol).

      Let's plug SchemaSychronizationManager into Ignite node and use it for waiting actual metadata before resolve actual Catalog version for a transaction.

      Attachments

        Issue Links

          is caused by

          Improvement - An improvement or enhancement to an existing feature or task. IGNITE-19770 Add a mechanism to wait till a schema is available via Schema Sync at a ts

          • Major - Major loss of function.
          • Resolved
          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-18733 Mechanism to synchronize database schema changes between nodes

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              ibessonov Ivan Bessonov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: