phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ravi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1028) Prevent declaration of non PK columns as NOT NULL
Date Mon, 09 Jun 2014 04:28:01 GMT

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

ravi commented on PHOENIX-1028:
-------------------------------

Hi [~james@jamestaylor.org] ,
   In both the tests, I noticed only k1 column as the PK column. Hence, had to remove the
NOT NULL constraint. 



> Prevent declaration of non PK columns as NOT NULL
> -------------------------------------------------
>
>                 Key: PHOENIX-1028
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1028
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: maghamravikiran
>         Attachments: 0001-PHOENIX-1028.patch
>
>
> The following statement should issue an error, as we're not able to enforce not null
constraints for non PK columns (i.e. ENTRY_POINT_NAME  column):
> {code}
> CREATE TABLE IF NOT EXISTS EVENT.APEX_LIMIT (
>     ORGANIZATION_ID CHAR(15) NOT NULL,
>     EVENT_TIME DATE NOT NULL,
>     USER_ID CHAR(15) NOT NULL,
>     ENTRY_POINT_ID CHAR(15) NOT NULL,
>     ENTRY_POINT_TYPE CHAR(2) NOT NULL,
>     APEX_LIMIT_ID CHAR(15) NOT NULL, 
>     USERNAME CHAR(80),  
>     NAMESPACE_PREFIX VARCHAR,
>     ENTRY_POINT_NAME VARCHAR NOT NULL,
>     EXECUTION_UNIT_NO VARCHAR,
>     LIMIT_TYPE VARCHAR,
>     LIMIT_VALUE DOUBLE  
>     CONSTRAINT PK PRIMARY KEY 
>     (
>         ORGANIZATION_ID, 
>         EVENT_TIME,
>         USER_ID,
>         ENTRY_POINT_ID,
>         ENTRY_POINT_TYPE,        
>         APEX_LIMIT_ID
>     ) 
> ) VERSIONS=1,MULTI_TENANT=true, SALT_BUCKETS=64
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message