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.6
    • 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

          Activity

            People

              holyfoot Alexey Botchkov
              monty Michael Widenius
              Votes:
              3 Vote for this issue
              Watchers:
              15 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.