[jira] [Commented] (IGNITE-5264) DDL operations must operate on per-schema basis
[ https://issues.apache.org/jira/browse/IGNITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021052#comment-16021052 ] ASF GitHub Bot commented on IGNITE-5264: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1990 > DDL operations must operate on per-schema basis > --- > > Key: IGNITE-5264 > URL: https://issues.apache.org/jira/browse/IGNITE-5264 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > Currently we rely on cache name in schema operations. Schema should be used > instead: > 1) Start missing caches in case of "TABLE NOT FOUND" and "INDEX NOT FOUND" > errors as well; > 2) Pass schema name to {{SchemaChangeOperation}} instead of cache name. > 3) Concurrency control on per-schema basis in {{GridQueryProcessor}}. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5264) DDL operations must operate on per-schema basis
[ https://issues.apache.org/jira/browse/IGNITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020967#comment-16020967 ] Vladimir Ozerov commented on IGNITE-5264: - Tests looks fine. > DDL operations must operate on per-schema basis > --- > > Key: IGNITE-5264 > URL: https://issues.apache.org/jira/browse/IGNITE-5264 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > Currently we rely on cache name in schema operations. Schema should be used > instead: > 1) Start missing caches in case of "TABLE NOT FOUND" and "INDEX NOT FOUND" > errors as well; > 2) Pass schema name to {{SchemaChangeOperation}} instead of cache name. > 3) Concurrency control on per-schema basis in {{GridQueryProcessor}}. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-5264) DDL operations must operate on per-schema basis
[ https://issues.apache.org/jira/browse/IGNITE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020806#comment-16020806 ] ASF GitHub Bot commented on IGNITE-5264: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1990 IGNITE-5264 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5264 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1990.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 #1990 commit e04c785c3ef7426a8aa11658655dfc43511a9836 Author: devozerovDate: 2017-05-22T14:26:43Z Preparing. commit 03daf6dc305a010b4451d61e7f01a717c67fe8c5 Author: devozerov Date: 2017-05-23T07:29:57Z Removed schema key. commit a640720c6db52c4d2ea7ddf1523a97cab267fef4 Author: devozerov Date: 2017-05-23T08:00:08Z Finalization. commit 217ba052f5578b2612bd9525a1095a0bb9b06c43 Author: devozerov Date: 2017-05-23T08:30:30Z WOrks fine. > DDL operations must operate on per-schema basis > --- > > Key: IGNITE-5264 > URL: https://issues.apache.org/jira/browse/IGNITE-5264 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 2.1 > > > Currently we rely on cache name in schema operations. Schema should be used > instead: > 1) Start missing caches in case of "TABLE NOT FOUND" and "INDEX NOT FOUND" > errors as well; > 2) Pass schema name to {{SchemaChangeOperation}} instead of cache name. > 3) Concurrency control on per-schema basis in {{GridQueryProcessor}}. -- This message was sent by Atlassian JIRA (v6.3.15#6346)