You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/04/17 12:03:00 UTC
[jira] [Updated] (IGNITE-7236) SQL: create tests for optimized
INSERT and MERGE operations
[ https://issues.apache.org/jira/browse/IGNITE-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Gura updated IGNITE-7236:
--------------------------------
Fix Version/s: (was: 2.5)
2.6
> SQL: create tests for optimized INSERT and MERGE operations
> -----------------------------------------------------------
>
> Key: IGNITE-7236
> URL: https://issues.apache.org/jira/browse/IGNITE-7236
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Alexander Paschenko
> Priority: Major
> Fix For: 2.6
>
>
> Important optimization IGNITE-4490 was added to the product. However, it lacks excessive tests coverage. We need to test the following scenarios:
> 1) Various data types (especially dates)
> 2) Single updates vs batched updates
> 3) Constants and nulls (e.g. {{INSERT INTO ... VALUES (a, b)}})
> 4) Parameters (e.g. {{INSERT INTO ... VALUES (?, ?)}})
> 5) Multiple SQL statements at once (e.g. {{INSERT INTO ...; INSERT INTO ...}})
> 6) Insert multiple lines at once ({{INSERT INTO ... VALUES (a1, b1), (a2, b2)}})
> 7) Insert multiple lines with parameters
> 8) Invalid parameters count in different query types - need to make sure that we throw correct errors.
> All tests except of p.8 should check both correctness and the fact that query was executed without H2 involvement (e.g. using some code hack).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)