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] [Assigned] (IGNITE-4953) Rework logic of concurrent schema changes
Date Sat, 15 Apr 2017 14:54:41 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov reassigned IGNITE-4953:
---------------------------------------

    Resolution: Fixed
      Assignee: Vladimir Ozerov  (was: Alexander Paschenko)

> 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: Vladimir Ozerov
>              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