[
https://issues.apache.org/jira/browse/IGNITE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255383#comment-16255383
]
ASF GitHub Bot commented on IGNITE-6932:
----------------------------------------
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3048
IGNITE-6932 GridQueryProcessor.querySqlFieldsNoCache should check for…
… cluster active/inactive state
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6932
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3048.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3048
----
commit 0601c1ba628556c4f5be82063dae111658f57a46
Author: tledkov-gridgain <[email protected]>
Date: 2017-11-16T14:18:03Z
IGNITE-6932 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)
