[
https://issues.apache.org/jira/browse/IGNITE-6403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170457#comment-16170457
]
ASF GitHub Bot commented on IGNITE-6403:
----------------------------------------
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2688
IGNITE-6403 SchemaOperationManager fix
…tiated operation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6403
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2688.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 #2688
----
commit 6a95a845056e7d509ad3fcf78738f1d59f7cc892
Author: Alexander Paschenko <alexander.a.pasche...@gmail.com>
Date: 2017-09-18T18:04:57Z
IGNITE-6403 SchemaOperationManager always waits for node that has initiated
operation.
----
> 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)
