[
https://issues.apache.org/jira/browse/IGNITE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177687#comment-15177687
]
Sergi Vladykin commented on IGNITE-1232:
----------------------------------------
When you run query on replicated cache it is assumed that we don't need to do
any additional processing, but run the query locally, this always worked like
that, I don't see any reason to change it now. This issue is unrelated to
distributed joins. I think we should throw exception if user tries to run query
with enabled distributedJoin flag on replicated cache, because it is
meaningless with current semantics of replicated query.
It is an interesting case when cache does not participate in the query. I think
first we have to find out the reason of this wrong result, then decide. Also
did we check if we have a correct result without distributedJoin enabled for
this case? I believe this issue is unrelated to distributedJoins as well.
> Support distributed SQL JOIN
> -----------------------------
>
> Key: IGNITE-1232
> URL: https://issues.apache.org/jira/browse/IGNITE-1232
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergi Vladykin
> Assignee: Sergi Vladykin
> Fix For: 1.6
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
