[
https://issues.apache.org/jira/browse/IGNITE-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038775#comment-16038775
]
ASF GitHub Bot commented on IGNITE-5306:
----------------------------------------
GitHub user kdudkov opened a pull request:
https://github.com/apache/ignite/pull/2094
IGNITE-5306 persist sql flag
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5306
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2094.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 #2094
----
commit cc4e3147d11416d29849a4173dde96e4fd31116b
Author: Konstantin Dudkov <[email protected]>
Date: 2017-06-06T12:02:28Z
IGNITE-5306 persist sql flag
----
> Make sure that SQL context is persisted along with cache configuration
> ----------------------------------------------------------------------
>
> Key: IGNITE-5306
> URL: https://issues.apache.org/jira/browse/IGNITE-5306
> Project: Ignite
> Issue Type: Task
> Components: cache, persistence, sql
> Reporter: Vladimir Ozerov
> Assignee: Konstantin Dudkov
> Fix For: 2.1
>
>
> This ticket should be implemented after IGNITE-5242 is ready. When we create
> cache using {{CREATE TABLE}} command, we set special {{sql}} flag to
> {{DynamicCacheDescriptor}}. This flag controls whether this cache can be
> dropped through {{DROP TABLE}} command or not.
> When persisting cache configuration we should also persist this flag, and
> restore it afterwards.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
