phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-3398) ROW_TIMESTAMP set in CONSTRAINT field does not set isRowTimestamp in ColumnDef
Date Sun, 23 Oct 2016 04:55:58 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor resolved PHOENIX-3398.
-----------------------------------
    Resolution: Invalid

This is working as designed, as the isRowTimestamp is stored in the PrimaryKeyConstraint if
defined in the primary key constraint and recognized during the create table process in MetaDataClient.


> ROW_TIMESTAMP set in CONSTRAINT field does not set isRowTimestamp in ColumnDef
> ------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3398
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3398
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.0
>            Reporter: Kevin Liew
>
> The following DDL will result in `isRowTimestamp` being set in ColumnDef.
> {code:java}
>         String ddl = "CREATE TABLE IF NOT EXISTS " + table + " ("
>                 + "pk BIGINT DEFAULT 5 PRIMARY KEY ROW_TIMESTAMP)";
> {code}
> The following DDL will not:
> {code:java}
>         String ddl = "CREATE TABLE IF NOT EXISTS " + table + " ("
>                 + "pk1 INTEGER NOT NULL,"
>                 + "pk2 BIGINT NOT NULL DEFAULT 5,"
>                 + "CONSTRAINT NAME_PK PRIMARY KEY (pk1, pk2 ROW_TIMESTAMP))";
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message