Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4259

transactional DDL

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      What does it mean, ACID? Rollback-ability? MVCC?

      I suppose this intuitively means that a DDL could be part of a larger transaction and could be rolled back with it.

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. MDEV-17567 Atomic DDL

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-25292 Atomic CREATE OR REPLACE TABLE

          • Critical - Crashes, loss of data, severe memory leak.
          • In Testing

          New Feature - A new feature of the product, which has yet to be developed. MDEV-25920 Atomic DROP DATABASE

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. MDEV-25921 Implement CREATE TABLE...SELECT in one transaction

          • Major - Major loss of function.
          • Open
          relates to

          Task - A task that needs to be done. MDEV-3808 Better table discovery

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-11655 Transactional data dictionary

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18097 Indicate which InnoDB data files are zero-initialized

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-25180 Atomic ALTER TABLE

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-4783 New .frm file format

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Task - A task that needs to be done. MDEV-34461 Transactional TRUNCATE

          • Major - Major loss of function.
          • Open
          links to

          Web Link WL#4180: Persistent object versions

          Activity

            Ascending order - Click to sort in descending order
            serg Sergei Golubchik created issue -
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            serg Sergei Golubchik made changes -
            rspadim roberto spadim made changes -
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Assignee Michael Widenius [ monty ]
            monty Michael Widenius made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            serg Sergei Golubchik made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Priority Major [ 3 ] Blocker [ 1 ]
            serg Sergei Golubchik made changes -
            Assignee Michael Widenius [ monty ] Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Workflow defaullt [ 26527 ] MariaDB v2 [ 44702 ]
            serg Sergei Golubchik made changes -
            Priority Blocker [ 1 ] Critical [ 2 ]
            serg Sergei Golubchik made changes -
            Description After MDEV-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs - we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC. After MDEV-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs — we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC.
            serg Sergei Golubchik made changes -
            Fix Version/s 10.1 [ 16100 ]
            Fix Version/s 10.1.0 [ 12200 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.2.0 [ 14601 ]
            Fix Version/s 10.1 [ 16100 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Workflow MariaDB v2 [ 44702 ] MariaDB v3 [ 64069 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.2 [ 14601 ]
            manjot Manjot Singh (Inactive) made changes -
            monty Michael Widenius made changes -
            marko Marko Mäkelä made changes -
            ralf.gebhardt Ralf Gebhardt made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 64069 ] MariaDB v4 [ 130098 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            ralf.gebhardt Ralf Gebhardt made changes -
            AirFocus AirFocus made changes -
            Description After MDEV-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs — we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC. After MDEV\-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs — we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC.
            julien.fritsch Julien Fritsch made changes -
            Description After MDEV\-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs — we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC. After MDEV-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs — we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC.
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            julien.fritsch Julien Fritsch made changes -
            Issue Type Task [ 3 ] New Feature [ 2 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Description After MDEV-3808 we have persistent table metadata versions stored in frm files. This allows to implement transactional DDLs — we need to add the version to the table key, then different versions of the same table will be able to coexist in the TDC. I suppose this intuitively means that a DDL could be part of a larger transaction and could be rolled back with it.
            serg Sergei Golubchik made changes -
            Description I suppose this intuitively means that a DDL could be part of a larger transaction and could be rolled back with it. What does it mean, ACID? Rollback-ability? MVCC?

            I suppose this intuitively means that a DDL could be part of a larger transaction and could be rolled back with it.
            mariadb-jira-automation Jira Automation (IT) made changes -
            Zendesk Related Tickets 189962

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              30 Vote for this issue
              Watchers:
              32 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.