[
https://issues.apache.org/jira/browse/IGNITE-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543192#comment-16543192
]
ASF GitHub Bot commented on IGNITE-8060:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4359
IGNITE-8060 IGNITE-8055
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8060
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4359.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 #4359
----
commit 2b9a0f46b7ca37cfd00cac6eb5e0ecda74884ca0
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-07-13T11:41:39Z
IGNITE-8060 Start missing caches before executing operations on all caches.
commit e732561681cd6e62978b07f7ab4116797ecda2a3
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-07-13T11:42:55Z
IGNITE-8055 Start missing caches even if "IF EXISTS" not in query.
----
> Sqline creating tables on client nodes works incorrect in case of node's
> shutdown
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-8060
> URL: https://issues.apache.org/jira/browse/IGNITE-8060
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.4
> Reporter: Andrey Aleksandrov
> Assignee: Ilya Kasnacheev
> Priority: Major
> Fix For: 2.7
>
> Attachments: ignite-76cc6387.log, ignite-a1c90af9.log
>
>
> For reproducing (master branch)
> You should start one local server and one local client nodes and follow the
> instructions:
> 1)Connect to client node:
> sqlline.bat --color=true --verbose=true -u jdbc:ignite:thin://127.0.0.1:10801
> 2)Create new table on client node:
> CREATE TABLE City (id LONG PRIMARY KEY, name VARCHAR)WITH
> "template=replicated";
> 3)Check that table exists from server node:
> !tables
> On this step table should be shown in the response.
> 4)Drop the client node
> 5)Create new client node
> 6)Connect to new client node:
> sqlline.bat --color=true --verbose=true -u jdbc:ignite:thin://127.0.0.1:10801
> 7)Check that table exists from server node:
> !tables
> *On this step there is no "city" table in the list.*
> 8)Try to drop the table:
> DROP TABLE City;
> java.sql.SQLException: Table doesn't exist: CITY
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 9)Try to create new table:
> CREATE TABLE City (id LONG PRIMARY KEY, name VARCHAR)WITH
> "template=replicated";
> java.sql.SQLException: Table already exists: CITY
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> Update:
> Exceptions on CREATE/REMOVE are thrown only until first SELECT isn't done.
> !tables doen\t work even after SELECT
> SELECT works OK.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
