[jira] [Updated] (IGNITE-10971) SQL: Support partition pruning for distributed joins

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

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

Maxim Muzafarov updated IGNITE-10971:
-------------------------------------
    Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)

> SQL: Support partition pruning for distributed joins
> ----------------------------------------------------
>
>                 Key: IGNITE-10971
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10971
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.9
>
>
> During IGNITE-10307 implementation it was revealed that distributed joins do not work with partition pruning. We never observed it before because it was impossible to derive partitions from joins.
> The problem appears as timeout exception from reducer due to some timeouts/retries inside distributed joins logic. Failures could be reproduced as follows:
> 1) Remove {{GridSqlQuerySplitter.distributedJoins}} usage which prevents partition to be derived for map query.
> 2) Run any of the following tests and observe that some of tests cases fails with reducer timeout:
> {{IgniteSqlSplitterSelfTest}}
> {{IgniteCacheJoinQueryWithAffinityKeyTest}}
> {{IgniteCacheDistributedJoinQueryConditionsTest}}
> {{IgniteCacheCrossCacheJoinRandomTest}}
> Root cause is unknown, but most likely this is due some missing messages, because some parts of distributed join engine is not aware of extracted partitions and await for replies from not involved nodes.
> Note that most likely the same problem will appear for queries with distributed joins and explicit partitions ({{SqlFieldsQuery.partitions}}).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)