[jira] [Updated] (IGNITE-15013) Design the transaction protocol for Ignite 3
[ https://issues.apache.org/jira/browse/IGNITE-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15013: --- Epic Link: IGNITE-15081 > Design the transaction protocol for Ignite 3 > > > Key: IGNITE-15013 > URL: https://issues.apache.org/jira/browse/IGNITE-15013 > Project: Ignite > Issue Type: Task >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: iep-61, ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > As a result of this task, the transactional protocol design must be proposed. > It's ok to have a protocol design to be in some intermediate state, so, not > all desired features can be available. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15013) Design the transaction protocol for Ignite 3
[ https://issues.apache.org/jira/browse/IGNITE-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15013: --- Labels: iep-61 ignite-3 (was: ignite-3) > Design the transaction protocol for Ignite 3 > > > Key: IGNITE-15013 > URL: https://issues.apache.org/jira/browse/IGNITE-15013 > Project: Ignite > Issue Type: Task >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: iep-61, ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > As a result of this task, the transactional protocol design must be proposed. > It's ok to have a protocol design to be in some intermediate state, so, not > all desired features can be available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15013) Design the transaction protocol for Ignite 3
[ https://issues.apache.org/jira/browse/IGNITE-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15013: --- Description: As a result of this task, the transactional protocol design must be proposed. It's ok to have a protocol design to be in some intermediate state, so, not all desired features can be available. was: This is a top level issue for implementing tx support in Ignite 3 As a result of this task, the transactional protocol design must be proposed and a prototype implementation like isolated tx subsystem should be merged to the master. It's ok to have a protocol design to be in some intermediate state, so, not all desired features can be available. > Design the transaction protocol for Ignite 3 > > > Key: IGNITE-15013 > URL: https://issues.apache.org/jira/browse/IGNITE-15013 > Project: Ignite > Issue Type: Task >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > As a result of this task, the transactional protocol design must be proposed. > It's ok to have a protocol design to be in some intermediate state, so, not > all desired features can be available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15013) Design the transaction protocol for Ignite 3
[ https://issues.apache.org/jira/browse/IGNITE-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15013: --- Summary: Design the transaction protocol for Ignite 3 (was: Design and prototype the transaction protocol for Ignite 3) > Design the transaction protocol for Ignite 3 > > > Key: IGNITE-15013 > URL: https://issues.apache.org/jira/browse/IGNITE-15013 > Project: Ignite > Issue Type: Task >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > This is a top level issue for implementing tx support in Ignite 3 > As a result of this task, the transactional protocol design must be proposed > and a prototype implementation like isolated tx subsystem should be merged to > the master. > It's ok to have a protocol design to be in some intermediate state, so, not > all desired features can be available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
