You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/03/20 08:54:00 UTC

[jira] [Assigned] (IGNITE-7359) SQL: DDL synchronization with query and cache API operations

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

Vladimir Ozerov reassigned IGNITE-7359:
---------------------------------------

    Assignee: Sergey Kalashnikov  (was: Vladimir Ozerov)

> SQL: DDL synchronization with query and cache API operations
> ------------------------------------------------------------
>
>                 Key: IGNITE-7359
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7359
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.4
>            Reporter: Sergey Kalashnikov
>            Assignee: Sergey Kalashnikov
>            Priority: Major
>             Fix For: 2.5
>
>
> We need to add a means to synchronize DDL operations with queries and cache operations. This is required to facilitate future DDL improvements that would require to modify user data and/or some cache metadata atomically. Basically it is a sort of a global table lock.
> One way to achieve this is to re-use a mechanism used by the exchange procedure. 
> An exchange is waiting for all already started cache operations to end before proceeding itself.
> Likewise, the new cache operations won't start until exchange procedure has completed.
> However, for DDL we only need to selectively defer operations that are made on the same cache as DDL operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)