ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-8060) Sqline creating tables on client nodes works incorrect in case of node's shutdown
Date Tue, 14 Aug 2018 10:21:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ilya Kasnacheev reassigned IGNITE-8060:
---------------------------------------

    Assignee:     (was: Ilya Kasnacheev)

> 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
>            Priority: Major
>         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)

Mime
View raw message