phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4183) Disallow creating an index on a mutable table that has a row_timestamp column
Date Wed, 27 Sep 2017 06:43:00 GMT

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

Thomas D'Silva updated PHOENIX-4183:
------------------------------------
    Summary: Disallow creating an index on a mutable table that has a row_timestamp column
 (was: Disallow UPSERT that specifies ROW_TIMESTAMP column value for table with mutable index)

> Disallow creating an index on a mutable table that has a row_timestamp column
> -----------------------------------------------------------------------------
>
>                 Key: PHOENIX-4183
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4183
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Thomas D'Silva
>             Fix For: 4.12.0
>
>
> When a table has row_timestamp column, user provided value for the column ends up being
the timestamp of the corresponding mutation. This could be problematic for our mutable indexes.
Immutable tables and indexes are fine, though. We should detect this when the UPSERT is performed
and give an error.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message