You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/03/19 11:27:00 UTC

[jira] [Updated] (IGNITE-21801) Add missing integration tests on Schema Sync

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

Roman Puchkovskiy updated IGNITE-21801:
---------------------------------------
    Description: 
# Verify that, if an RW transaction is started, and then a write is made to a table in this transaction, then the table is dropped and then the transaction is tried to be committed, the commit fails
 # Verify that, if an RW tx1 is started, then table T schema is changed (for example, a column is added), then a put is made to table T for key K in an implicit transaction tx2 (so it gets committed), and then tx1 tries to read K (either directly or using a scan), the read fails
 # Verify that the schemaSync.delayDuration configuration property is immutable (cannot be changed after the cluster has been initialized).

> Add missing integration tests on Schema Sync
> --------------------------------------------
>
>                 Key: IGNITE-21801
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21801
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> # Verify that, if an RW transaction is started, and then a write is made to a table in this transaction, then the table is dropped and then the transaction is tried to be committed, the commit fails
>  # Verify that, if an RW tx1 is started, then table T schema is changed (for example, a column is added), then a put is made to table T for key K in an implicit transaction tx2 (so it gets committed), and then tx1 tries to read K (either directly or using a scan), the read fails
>  # Verify that the schemaSync.delayDuration configuration property is immutable (cannot be changed after the cluster has been initialized).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)