ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10824) SQL: mixing _key and key columns in the DML queries must be disallowed
Date Thu, 24 Jan 2019 13:06:00 GMT

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

Pavel Kuznetsov commented on IGNITE-10824:
------------------------------------------

Thank you!
p 2 - Yes I see, this is consequence of my "fail fast" changes. Fixed that.
Also I see that other tests that was introduced during IGNITE-4363 should be fixed. Their
goal is to test operations on the nested fields, but their implementation inserts entire _key/_val
and updates nested field as one operation. Now I should split this operation to 2 separated
operations.

> SQL: mixing _key and key columns in the DML queries must be disallowed
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-10824
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10824
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Pavel Kuznetsov
>            Assignee: Pavel Kuznetsov
>            Priority: Minor
>             Fix For: 2.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> DML should contain either placeholder for _key (_val) or subset of key (value) columns
but not both. Also we should keep in mind _key/_value aliases
> Given table with primary key column {{id}} and value column {{salary}}. Next queries
should be validated to parsing error:
> {code:sql}
> INSERT INTO TEST_TABLE (_key, id, salary) VALUES (1, 2, 42);
> UPDATE TEST_TABLE SET _val = 1, salary = 2;
> {code}   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message