[jira] [Commented] (IGNITE-5422) CREATE TABLE command should support all-key fields case

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-5422:
----------------------------------------

GitHub user alexpaschenko opened a pull request:

    https://github.com/apache/ignite/pull/2100

    IGNITE-5422

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5422

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2100.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2100
    
----
commit 7698dd35c39bd636e9386e25e29a108acd815886
Author: Alexander Paschenko <al...@gmail.com>
Date:   2017-06-07T09:51:48Z

    IGNITE-5422 CREATE TABLE with no value columns.

commit f481f9e73ec3278df7d8cb91017414b042682433
Author: Alexander Paschenko <al...@gmail.com>
Date:   2017-06-07T09:52:25Z

    Merge remote-tracking branch 'apache/master' into ignite-5422

----


> CREATE TABLE command should support all-key fields case
> -------------------------------------------------------
>
>                 Key: IGNITE-5422
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5422
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Assignee: Alexander Paschenko
>             Fix For: 2.2
>
>
> Currently it is impossible to create a table containing only {{PRIMARY KEY}} columns:
> {code}
> CREATE TABLE PersonProject {
>     person_id BIGINT,
>     project_id BIGINT,
>     PRIMARY KEY (person_id, project_id);
> };
> {code}
> The reason for this limitation is that we have nothing to be saved as cache value and {{null}} values are restricted because they are indistinguishable from removal.
> We should allow this case somehow. Possible solutions:
> 1) Save empty object of table type: {{IgniteBinary.builder("PersonProject").build()}}
> 2) Save {{false}} as it is done in Java in Map-to-Set conversion
> Note that DML processing should be adjusted accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)