[jira] [Commented] (IGNITE-4953) Rework logic of concurrent schema changes

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

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

Vladimir Ozerov commented on IGNITE-4953:
-----------------------------------------

[~al.psc],
Please see my branch {{ignite-4953-1}} where I polished several problems during review. However, it doesn't work still. The problem is that H2 knows nothing about indexes created on table initialization phase. For this reason {{DynamicIndexBasicClientSelfTest.testDrop}} fails with {{Index "IDX_1" not found}} exception thrown from H2 internals.

> Rework logic of concurrent schema changes
> -----------------------------------------
>
>                 Key: IGNITE-4953
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4953
>             Project: Ignite
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.0
>            Reporter: Alexander Paschenko
>            Assignee: Alexander Paschenko
>              Labels: important
>             Fix For: 2.0
>
>
> H2's prepared statements store references to indexes that were present when the statement was parsed and initialized - this means that currently there's no way to prevent index usage if it goes down between the moment when the statement is created and actually executed. Have to come up with some new locking schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)