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

Evgeny Stanilovsky commented on IGNITE-18994:
---------------------------------------------

[~alapin] i found that test_big_insert.test_ignore annotated with this issue is 
correctly passed, but test_scan_big_varchar.test_slow (after removing _skipif 
ignite3_ annotation) still broken, does it means it already fixed for some 
cases ? Remind - to check exact test you need to specify it as :

{noformat}
@SqlLogicTestEnvironment(scriptsRoot = "src/integrationTest/sql", regex = 
"test_scan_big_varchar.test_slow")
public class ItSqlLogicTest extends IgniteIntegrationTest {
{noformat}


> SQL requests within RW transactions should not see their own changes.
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-18994
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18994
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>
> Following requests
> {code:java}
> INSERT INTO bigtable SELECT * FROM bigtable{code}
> should not see their own changes.
> Consider following reproducer for more details:
> {code:java}
>     // ItDmlTest.java
>     @Test
>     @WithSystemProperty(key = "IMPLICIT_PK_ENABLED", value = "true")
>     public void test() {
>         sql("CREATE TABLE test (x INT)");
>         long size = 1024;
>         // initial state
>         sql("INSERT INTO test SELECT * FROM TABLE(system_range(1, ?))", size);
>         for (int i = 0; i < 5; i++) {
>             sql("INSERT INTO test SELECT * FROM test");
>             assertQuery("SELECT count(*) FROM test")
>                     .returns(size * 2)
>                     .check();
>             size *= 2;
>         }
>     } {code}



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

Reply via email to