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

Multi-version concurrency control

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.7
    • cache

    Description

      Current Ignite SQL does not take into account transaction boundaries. For example, if a transaction atomically changes balance of two accounts, then a concurrent SQL query can see partially committed transaction. This works for data analytics, but does not work for more strict and demanding scenarios.

      It would be perfect if we had a mode which ensures transaction boundaries are taken into account for SQL query.

      Attachments

        Issue Links

          contains

          Task - A task that needs to be done. IGNITE-6874 MVCC: base functionality

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. IGNITE-6875 MVCC: advanced features

          • Major - Major loss of function.
          • Closed
          Is contained by

          New Feature - A new feature of the product, which has yet to be developed. IGNITE-4191 SQL: support transactions

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              agoncharuk Alexey Goncharuk
              Votes:
              10 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: