Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5874

Evaluation for Cross Engine Join only single-table queries processing

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • None
    • 23.10.5
    • MDB Plugin
    • None

    Description

      This issue describes a new feature enables processing of foreign engines queries, e.g. InnoDB. Consider a query

      SELECT count(*) from non_mcs where c1 > 5;
      

      or

      SELECT count(*) from non_mcs1 t1, non_mcs2 t2 where t1.c1 = t2.c1;
      

      Given there is a mechanism to hand such queries over to MCS SELECT handler one has to alter a number of facilities to enable processing for single table queries.
      This issue is supposed to deliver evaluation for a single foreign table query performance, .e.g count() with an explicit GROUP BY uses key columns that don't belong to Innodb index.
      The mentioned handover mechanism in the context of this issue would be a temporary shortcut that conditionally hands over processing of a query down to MCS.
      As of now CrossEngineStep is an equivalent of TBPS that implements TupleDeliveryStep interface thus can be the source step of a JobList.

      Attachments

        Issue Links

          Activity

            People

              drrtuy Roman
              drrtuy Roman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 20d
                  20d
                  Remaining:
                  0d
                  Logged:
                  Time Not Required
                  Not Specified

                  Git Integration

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