ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8693) SQL JOIN between PARTITIONED and REPLICATED cache fails
Date Mon, 04 Jun 2018 13:02:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500174#comment-16500174

ASF GitHub Bot commented on IGNITE-8693:

GitHub user ilantukh opened a pull request:


    IGNITE-8693 : Fix for SQL JOIN between REPLICATED and PARTITIONED caches


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8693

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4120
commit 9b4ae6520c9c701382bc5468141c4b709658f682
Author: Ilya Lantukh <ilantukh@...>
Date:   2018-06-01T14:01:43Z

    ignite-8693 : Fix for SQL JOIN between REPLICATED and PARTITIONED caches.


> SQL JOIN between PARTITIONED and REPLICATED cache fails
> -------------------------------------------------------
>                 Key: IGNITE-8693
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8693
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ilya Lantukh
>            Assignee: Ilya Lantukh
>            Priority: Major
> One case of such problem is reproduced by IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> If PARTITIONED cache has NodeFilter and is located on subset of REPLICATED cache nodes,
we might fail to execute SQL JOIN query with "Caches have distinct sets of data nodes" error.
Whether if will fail or not depends on order of *cacheIds* List argument in GridReduceQueryExecutor.stableDataNodes(...)
- we will fail if first cacheId is REPLICATED. The order depends on internal factors that
are out of user's control.

This message was sent by Atlassian JIRA

View raw message