[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Labels: (was: mvcc) > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, mvcc, sql >Reporter: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Labels: mvcc (was: ) > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, mvcc, sql >Reporter: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Component/s: mvcc > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, mvcc, sql >Reporter: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Labels: (was: iep-3) > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, mvcc, sql >Reporter: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6936: --- Fix Version/s: (was: 2.6) 2.7 > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Priority: Major > Labels: iep-3 > Fix For: 2.7 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov updated IGNITE-6936: - Fix Version/s: (was: 2.5) 2.6 > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Priority: Major > Labels: iep-3 > Fix For: 2.6 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Fix Version/s: (was: 2.4) 2.5 > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov > Labels: iep-3 > Fix For: 2.5 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Labels: iep-3 (was: ) > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov > Labels: iep-3 > Fix For: 2.4 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6936: Security: (was: Public) > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov > Fix For: 2.4 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
