[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

["Vladimir Ozerov (JIRA)" <ji...@apache.org>]

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

Vladimir Ozerov commented on IGNITE-6403:
-----------------------------------------

[~al.psc], [~skalashnikov], I debugged the problem.

{{IgniteSqlNotNullConstraintTest}} performs all SQL operations against client node. And our DDL engine doesn't wait for clients to respond before completing client future. For this reason, by the time client is notified about successfull completion, it might not have applied changes yet. {{CREATE TABLE}} is not affected by this problem because we have special re-try logic for this. But {{ALTER TABLE}} is affected. I think {{CREATE INDEX}} is also broken.

When I changed the test so that SQL is executed on server nodes, everything works fine.

> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically
> -------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6403
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6403
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Assignee: Alexander Paschenko
>             Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 2), (3, 'ok', 3) [42122-195]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)