ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4953) Rework logic of concurrent schema changes
Date Sat, 15 Apr 2017 10:57:42 GMT

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

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

Another problem is that we use old {{GridH2TreeIndex}}, while new {{H2TreeIndex}} should be
used instead.

> 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)

Mime
View raw message