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

Supporting multiple engines with table partitioning

    XMLWordPrintable

Details

    • New Feature
    • Status: Stalled (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 11.9
    • Partitioning
    • None

    Description

      Allow different engines in a partitioned table.
      What is mostly needed is allow one to combine InnoDB with S3 tables but other combinations should be possible . InnoDB couldb be a OVERFLOW partition that handles all inserts while the other partitions are only used for read.

      From optimizer point of view, we should be AND the flags from all engines
      that is part of a query. If S3 and InnoDB is in the same query, we would
      loose the clustered key cost optimization, however I think we can survive
      without that.

      To support multiple engines, we probably also need to do MDEV-5271

      Attachments

        Issue Links

          blocks

          Technical task - A technical task. MDEV-28863 Galera testing of Support multiple engines in partitioning

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

          Task - A task that needs to be done. MDEV-29415 status and variables history via system-versioned tables parttion

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Open
          includes

          Task - A task that needs to be done. MDEV-5271 Support engine-defined attributes per partition

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15471 Assertion `new_clustered == ctx->need_rebuild()' failed in ha_innobase::commit_inplace_alter_table

          • Major - Major loss of function.
          • Stalled

          New Feature - A new feature of the product, which has yet to be developed. MDEV-27180 Fully atomic partitioning DDL operations

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22088 S3 partitioning support

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-27545 Feature request: migrate server attributes applicable to engines to the storage engine(s)

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27618 Atomic DDL is not very atomic on partitioned tables

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

          Activity

            People

              ycp Yuchen Pei
              monty Michael Widenius
              Votes:
              4 Vote for this issue
              Watchers:
              16 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.