You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/06/21 16:31:00 UTC

[jira] [Commented] (IGNITE-17045) SQL Cache Replicated - Select doesn't work

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

Evgeny Stanilovsky commented on IGNITE-17045:
---------------------------------------------

[~angelopingo] i don`t use kuber (and this is not an issue here), i check your case (with your config too), all ok for me:
can you clear db and recheck ? possible you connect to another instance or  smth else ? There are huge number of tests  for such cases and all ok there.

{noformat}
./sqlline.sh --verbose=true -u jdbc:ignite:thin://127.0.0.1/
issuing: !connect "jdbc:ignite:thin://127.0.0.1/"
Connecting to jdbc:ignite:thin://127.0.0.1/
Enter username for jdbc:ignite:thin://127.0.0.1/: 
Enter password for jdbc:ignite:thin://127.0.0.1/: 
Connected to: Apache Ignite (version 2.13.0#20220420-sha1:551f6ece)
Driver: Apache Ignite Thin JDBC Driver (version 2.13.0#20220420-sha1:551f6ece)
Autocommit status: true
Transaction isolation: TRANSACTION_REPEATABLE_READ
sqlline version 1.9.0
0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE test_table (
. . . . . . . . . . . . . . . .)>   field1 varchar,
. . . . . . . . . . . . . . . .)>   field2 BOOLEAN,
. . . . . . . . . . . . . . . .)>   PRIMARY KEY (field1)
. . . . . . . . . . . . . . . .)> ) WITH "template=Replicated";
No rows affected (0.162 seconds)
0: jdbc:ignite:thin://127.0.0.1/> INSERT INTO test_table (field1, field2) VALUES
. . . . . . . . . . . .semicolon>   ('field-value-1', true),
. . . . . . . . . . . .semicolon>   ('field-value-2', true, ),
. . . . . . . . . . . .semicolon>   ('field-value-3', false);
3 rows affected (0.089 seconds)
0: jdbc:ignite:thin://127.0.0.1/> SELECT * FROM test_table;
+---------------+--------+
|    FIELD1     | FIELD2 |
+---------------+--------+
| field-value-1 | true   |
| field-value-2 | true   |
| field-value-3 | false  |
+---------------+--------+
3 rows selected (0.06 seconds)

{noformat}


> SQL Cache Replicated - Select doesn't work
> ------------------------------------------
>
>                 Key: IGNITE-17045
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17045
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, sql
>    Affects Versions: 2.13
>         Environment: Official Helm for Kubernetes.
> Apache Ignite version 2.13.0.
> node-configuration.xml attached.
>            Reporter: Angelo Pingo
>            Priority: Blocker
>         Attachments: ignite-issue-partitioned.PNG, ignite-issue-replicated.PNG, node-configuration.xml
>
>
> I upgraded the Apache Ignite version from 2.12.0 to 2.13.0 and all my SQL Caches configured as Replicated mode does not work correctly (2.12.0 works fine). The table is created successfully and the inserts are done without any problem, but I can't select the inserted rows.
> Queries to reproduce the issue:
> CREATE TABLE test_table (
>   field1 varchar,
>   field2 BOOLEAN,
>   PRIMARY KEY (field1)
> ) WITH "template=Replicated";
> INSERT INTO test_table (field1, field2) VALUES
>   ('field-value-1', true),
>   ('field-value-2', true, ),
>   ('field-value-3', false);
> SELECT * FROM test_table;



--
This message was sent by Atlassian Jira
(v8.20.7#820007)