[
https://issues.apache.org/jira/browse/IGNITE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh updated IGNITE-8693:
---------------------------------
Description:
One case of such problem is reproduced by
IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (IGNITE-7766).
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.
> 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 (IGNITE-7766).
> 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
(v7.6.3#76005)
