[jira] [Assigned] (IGNITE-23746) Sql. ItSetOpTest uses incorrect optimizer hints for tests with Intersect operation

["Evgeny Stanilovsky (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-23746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evgeny Stanilovsky reassigned IGNITE-23746:
-------------------------------------------

    Assignee: Evgeny Stanilovsky

> Sql. ItSetOpTest uses incorrect optimizer hints for tests with Intersect operation
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-23746
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23746
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Maksim Zhuravkov
>            Assignee: Evgeny Stanilovsky
>            Priority: Minor
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> ItSetOpTest uses the same set of optimizer hints for both Minus and Intersect operations:
> {noformat}
>  public enum SetOpVariant {
>         COLOCATED("MapReduceMinusConverterRule"),
>         MAP_REDUCE("ColocatedMinusConverterRule");
>         final String[] disabledRules;
>         ...
>     }
> {noformat}
> and uses them in tests for both EXCEPT and INTERSECT operations. 
> When these rules are applied to EXCEPT queries then we get the desired behaviour (e.g. we check COLOCATED variant of EXCEPT operator when we disable MapReduceMinusConverterRule). But when these rules are applied to INTERSECT, it they do not have any affect because such nodes generated by different rules.
> Let's fix it by introducing another IntersectOpVariant and renaming SetOpVariant to MinusOpVariant.
>   



--
This message was sent by Atlassian Jira
(v8.20.10#820010)