You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/07 11:34:18 UTC
[jira] [Commented] (IGNITE-5431) Better exception message when SQL
cache flag doesn't match
[ https://issues.apache.org/jira/browse/IGNITE-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040737#comment-16040737 ]
ASF GitHub Bot commented on IGNITE-5431:
----------------------------------------
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2103
IGNITE-5431 Better handling of cache SQL flag incompatibility.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5431
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2103.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 #2103
----
commit c334090835e204ec4f3fa7c3931a34cc93aa20a3
Author: Alexander Paschenko <al...@gmail.com>
Date: 2017-06-07T11:31:26Z
IGNITE-5431 Better handling of cache SQL flag incompatibility.
----
> Better exception message when SQL cache flag doesn't match
> ----------------------------------------------------------
>
> Key: IGNITE-5431
> URL: https://issues.apache.org/jira/browse/IGNITE-5431
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> SQL flag configuration check is performed in {{ClusterCachesInfo>checkCache}}. Default validation mechanics is used and the following error message appears:
> {code}
> SQL flag mismatch (fix sql flag in cache configuration or set -DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property) [cacheName=SQL_PUBLIC_Person, localSql=false, remoteSql=true, rmtNodeId=b975316b-ad6a-4f64-b8a4-9eaac6400002]
> {code}
> Apparently, it is misleading because there is no such config property. Need to fix that and make sure that {{DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK}} has no effect on this check.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)