[
https://issues.apache.org/jira/browse/IGNITE-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080151#comment-16080151
]
Vladimir Ozerov commented on IGNITE-5422:
-----------------------------------------
Too risky for {{2.1}}. Moving to {{2.2}}.
> 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.4.14#64029)
