You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2022/06/02 10:28:00 UTC

[jira] [Updated] (IGNITE-17027) Incorrect result of the DML delete operation, in some environment

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

Yury Gerzhedovich updated IGNITE-17027:
---------------------------------------
    Component/s: sql

>  Incorrect result of the DML delete operation, in some environment
> ------------------------------------------------------------------
>
>                 Key: IGNITE-17027
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17027
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Luchnikov Alexander
>            Priority: Minor
>              Labels: ise
>         Attachments: IndexSetArgsAndCastTest.patch
>
>
> Description of the case, in some environment, the DML operation does not delete all data (this DML delete operation is an example). To reproduce the problem, you must:
> # Create a table with a varchar field.
> # Create an index on the given field.
> # Fill the table with data, use int as the value.
> # Delete data by specifying in the DML operation, as a condition, an indexed value, without String.valueOf(intValue)
> The reproducer( [^IndexSetArgsAndCastTest.patch] ) shows this behavior in indexOnAutocastOff() test.
> The result of all tests should be the same, specifically in this example (DML delete) - the number of entries in the cache, according to the result of each test, should be equal to zero.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)