Details
-
New Feature
-
Status: Stalled (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
-
None
-
None
-
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
- relates to
-
MCOL-5876 Evaluation for Cross Engine Join only multi-table queries processing
-
- Closed
-
-
MCOL-5882 Research statistics and partitioning methods available for innodb table
-
- Closed
-
-
MCOL-5883 Remove locale-related funcs used by dataconvert for CES data ingestion
-
- Closed
-
-
MCOL-5917 Query Accelerator | large dataset retrieval bug
-
- Closed
-