You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/04/17 10:02:00 UTC
[jira] [Commented] (IGNITE-6295) SQL: Get rid of "replicatedOnly"
flag
[ https://issues.apache.org/jira/browse/IGNITE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440697#comment-16440697 ]
Vladimir Ozerov commented on IGNITE-6295:
-----------------------------------------
Implementation notes:
1) \{{SqlFieldsQuery.isReplicatedOnly}} should not be used anymore
2) We should call parser before splitter and investigate whether all caches are \{{REPLICATED}} and has common data nodes. If yes - do not go through two-phase process, but generate the same query as for local mode and then execute it on random cache node.
> SQL: Get rid of "replicatedOnly" flag
> -------------------------------------
>
> Key: IGNITE-6295
> URL: https://issues.apache.org/jira/browse/IGNITE-6295
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Priority: Major
> Labels: performance, usability
>
> This flag acts as a hint that all tables are reside in {{REPLICATED}} cache. However, we already have this information in runtime! No need to ask users to think about it.
> Let's deprecate that flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)