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

ASF GitHub Bot commented on IGNITE-7359:
----------------------------------------

GitHub user skalashnikov opened a pull request:

    https://github.com/apache/ignite/pull/3386

    IGNITE-7359: prototype for ddl vs cache ops synchronization

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-7359

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3386.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 #3386
    
----
commit cdfa8803298fd7dd957cfcb176f6207356783395
Author: skalashnikov <skalashnikov@...>
Date:   2018-01-15T09:58:59Z

    IGNITE-7359: prototype for ddl vs cache ops synchronization

----


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

Reply via email to