[jira] [Updated] (IGNITE-7280) SQL TX: improve JDBC test coverage
[ https://issues.apache.org/jira/browse/IGNITE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7280: Component/s: mvcc > SQL TX: improve JDBC test coverage > -- > > Key: IGNITE-7280 > URL: https://issues.apache.org/jira/browse/IGNITE-7280 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko >Priority: Major > Fix For: 2.7 > > > The following cases must be handled: > 1) Single update stmt in TX > 2) Multiple update stmts in TX > 3) Changes to multiple caches in TX > 4) Mix of both selects and updates (e.g. get data from select and then build > updates based on it) > 5) Different operation types - INSERT, UPDATE, MERGE (take in count various > DML optimizations to ensure that as much code paths are covered as possible) > 6) Batch updates > 7) Joins (both co-located and distributed) > 8) Different cache modes - PARTITIONED, REPLICATED > 9) Different backup counts > 10) Communication with client node vs communication with server node > 11) Both implicit and explicit transactions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7280) SQL TX: improve JDBC test coverage
[ https://issues.apache.org/jira/browse/IGNITE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7280: --- Fix Version/s: (was: 2.6) 2.7 > SQL TX: improve JDBC test coverage > -- > > Key: IGNITE-7280 > URL: https://issues.apache.org/jira/browse/IGNITE-7280 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko >Priority: Major > Fix For: 2.7 > > > The following cases must be handled: > 1) Single update stmt in TX > 2) Multiple update stmts in TX > 3) Changes to multiple caches in TX > 4) Mix of both selects and updates (e.g. get data from select and then build > updates based on it) > 5) Different operation types - INSERT, UPDATE, MERGE (take in count various > DML optimizations to ensure that as much code paths are covered as possible) > 6) Batch updates > 7) Joins (both co-located and distributed) > 8) Different cache modes - PARTITIONED, REPLICATED > 9) Different backup counts > 10) Communication with client node vs communication with server node > 11) Both implicit and explicit transactions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7280) SQL TX: improve JDBC test coverage
[ https://issues.apache.org/jira/browse/IGNITE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov updated IGNITE-7280: - Fix Version/s: (was: 2.5) 2.6 > SQL TX: improve JDBC test coverage > -- > > Key: IGNITE-7280 > URL: https://issues.apache.org/jira/browse/IGNITE-7280 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko >Priority: Major > Fix For: 2.6 > > > The following cases must be handled: > 1) Single update stmt in TX > 2) Multiple update stmts in TX > 3) Changes to multiple caches in TX > 4) Mix of both selects and updates (e.g. get data from select and then build > updates based on it) > 5) Different operation types - INSERT, UPDATE, MERGE (take in count various > DML optimizations to ensure that as much code paths are covered as possible) > 6) Batch updates > 7) Joins (both co-located and distributed) > 8) Different cache modes - PARTITIONED, REPLICATED > 9) Different backup counts > 10) Communication with client node vs communication with server node > 11) Both implicit and explicit transactions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7280) SQL TX: improve JDBC test coverage
[ https://issues.apache.org/jira/browse/IGNITE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7280: Description: The following cases must be handled: 1) Single update stmt in TX 2) Multiple update stmts in TX 3) Changes to multiple caches in TX 4) Mix of both selects and updates (e.g. get data from select and then build updates based on it) 5) Different operation types - INSERT, UPDATE, MERGE (take in count various DML optimizations to ensure that as much code paths are covered as possible) 6) Batch updates 7) Joins (both co-located and distributed) 8) Different cache modes - PARTITIONED, REPLICATED 9) Different backup counts 10) Communication with client node vs communication with server node 11) Both implicit and explicit transactions was: The following cases must be handled: 1) Single update stmt in TX 2) Multiple update stmts in TX 3) Changes to multiple caches in TX 4) Mix of both selects and updates (e.g. get data from select and then build updates based on it) 5) Different operation types - INSERT, UPDATE, MERGE (take in count various DML optimizations to ensure that as much code paths are covered as possible) 6) Batch updates 7) Joins (both co-located and distributed) 8) Different cache modes - PARTITIONED, REPLICATED 9) Different backup counts 10) Communication with client node vs communcation with server node > SQL TX: improve JDBC test coverage > -- > > Key: IGNITE-7280 > URL: https://issues.apache.org/jira/browse/IGNITE-7280 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko > Fix For: 2.5 > > > The following cases must be handled: > 1) Single update stmt in TX > 2) Multiple update stmts in TX > 3) Changes to multiple caches in TX > 4) Mix of both selects and updates (e.g. get data from select and then build > updates based on it) > 5) Different operation types - INSERT, UPDATE, MERGE (take in count various > DML optimizations to ensure that as much code paths are covered as possible) > 6) Batch updates > 7) Joins (both co-located and distributed) > 8) Different cache modes - PARTITIONED, REPLICATED > 9) Different backup counts > 10) Communication with client node vs communication with server node > 11) Both implicit and explicit transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)