You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/09/20 06:24:20 UTC
[jira] [Commented] (PHOENIX-3298) Create Table: Single column
primary key may not be null
[ https://issues.apache.org/jira/browse/PHOENIX-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505747#comment-15505747 ]
James Taylor commented on PHOENIX-3298:
---------------------------------------
Phoenix assumes that a single column PK is not nullable because it doesn't allow a non nullable single column PK. Since we're parsing the create table statement, seems like we can handle this ourselves. We could deprecate this behavior potentially too and change the tests.
> Create Table: Single column primary key may not be null
> -------------------------------------------------------
>
> Key: PHOENIX-3298
> URL: https://issues.apache.org/jira/browse/PHOENIX-3298
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Eric Lomore
>
> Create table statements with a single column currently must have "NOT NULL" identifier to pass tests.
> Running this code results in failure
> {code}CREATE TABLE t (k VARCHAR PRIMARY KEY DESC){code}
> While this allows tests to pass
> {code}CREATE TABLE t (k VARCHAR NOT NULL PRIMARY KEY DESC){code}
> Must either enforce the not null condition and update test cases, or apply a fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)