[jira] [Commented] (IGNITE-5242) Disallow DROP TABLE on statically configured caches

2017-05-26 Thread Vladimir Ozerov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026121#comment-16026121
 ] 

Vladimir Ozerov commented on IGNITE-5242:
-

p.2 - got it.

> Disallow DROP TABLE on statically configured caches
> ---
>
> Key: IGNITE-5242
> URL: https://issues.apache.org/jira/browse/IGNITE-5242
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Should we allow {{DROP TABLE}} on statically configured cache, there will be 
> a room for weird situations when it is impossible to understand on whether to 
> start the cache or not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-5242) Disallow DROP TABLE on statically configured caches

2017-05-26 Thread Alexander Paschenko (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026106#comment-16026106
 ] 

Alexander Paschenko commented on IGNITE-5242:
-

[~vozerov]

1, 3: agree, working on fixes

2: these flags (don't fail if exists; fail if not started; check thread tx) 
match those used in routines like {{createFromTemplate}} with except for the 
first. It's false as we want to process false result and throw schema opeation 
exception from client code that calls this method ({{GridQueryProcessor}}, to 
be precise), not from cache processor internals.

> Disallow DROP TABLE on statically configured caches
> ---
>
> Key: IGNITE-5242
> URL: https://issues.apache.org/jira/browse/IGNITE-5242
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Should we allow {{DROP TABLE}} on statically configured cache, there will be 
> a room for weird situations when it is impossible to understand on whether to 
> start the cache or not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-5242) Disallow DROP TABLE on statically configured caches

2017-05-26 Thread Vladimir Ozerov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026043#comment-16026043
 ] 

Vladimir Ozerov commented on IGNITE-5242:
-

[~al.psc], my comments:
1) {{ClusterCachesInfo}}:817 - why false? Shouldn't we pass SQL flag here?
2) {{GridCacheProcessor.dynamicStartSqlCache}} - I do not understand flags you 
pass.
3) Not enough tests. You should also test node join scenario to ensure that SQL 
flag is propagated correctly between nodes, and that SQL-created cache cannot 
be "merged" with non-sql cache.

> Disallow DROP TABLE on statically configured caches
> ---
>
> Key: IGNITE-5242
> URL: https://issues.apache.org/jira/browse/IGNITE-5242
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Should we allow {{DROP TABLE}} on statically configured cache, there will be 
> a room for weird situations when it is impossible to understand on whether to 
> start the cache or not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (IGNITE-5242) Disallow DROP TABLE on statically configured caches

2017-05-23 Thread Alexander Paschenko (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021212#comment-16021212
 ] 

Alexander Paschenko commented on IGNITE-5242:
-

PR: https://github.com/apache/ignite/pull/1996

> Disallow DROP TABLE on statically configured caches
> ---
>
> Key: IGNITE-5242
> URL: https://issues.apache.org/jira/browse/IGNITE-5242
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Should we allow {{DROP TABLE}} on statically configured cache, there will be 
> a room for weird situations when it is impossible to understand on whether to 
> start the cache or not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)