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] [Updated] (PHOENIX-4183) Disallow UPSERT that specifies ROW_TIMESTAMP column value for table with mutable index
Date Wed, 20 Sep 2017 19:28:00 GMT

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

James Taylor updated PHOENIX-4183:
----------------------------------
    Description: 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.  (was: 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 global mutable indexes. Immutable tables and indexes are fine,
though.)

> Disallow UPSERT that specifies ROW_TIMESTAMP column value for table with mutable index
> --------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4183
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4183
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>
> 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