You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (JIRA)" <ji...@apache.org> on 2017/11/16 11:35:00 UTC
[jira] [Updated] (IGNITE-6932)
GridQueryProcessor.querySqlFieldsNoCache should check for cluster
active/inactive state
[ https://issues.apache.org/jira/browse/IGNITE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taras Ledkov updated IGNITE-6932:
---------------------------------
Summary: GridQueryProcessor.querySqlFieldsNoCache should check for cluster active/inactive state (was: GridQueryProcessorÑŽquerySqlFieldsNoCache should check for cluster active/inactive state)
> GridQueryProcessor.querySqlFieldsNoCache should check for cluster active/inactive state
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-6932
> URL: https://issues.apache.org/jira/browse/IGNITE-6932
> Project: Ignite
> Issue Type: Task
> Security Level: Public(Viewable by anyone)
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> Currently we do not check for this, so operation may hang silently. Let's add a check for this before starting query execution. See {{IgniteKernal.checkClusterState}} and it's usages.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)