[
https://issues.apache.org/jira/browse/IGNITE-6403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170484#comment-16170484
]
Vladimir Ozerov commented on IGNITE-6403:
-----------------------------------------
[~al.psc], root cause of the problem is that client nodes receive custom
discovery messages asynchronously. For this reason server node may complete
operations and notify the client before changes are appled to client schema. As
a result, we complete operations before local H2 is ready. To fix the problem
we should do the following:
1) Client future must consist of two parts - server part and local part.
2) Server part is completed in the same way it is implemented now.
3) Client part is completed when changes are applied on the client.
> 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)
