[jira] [Comment Edited] (PHOENIX-4183) Disallow creating mutable indexes on tables with ROW_TIMESTAMP column

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor edited comment on PHOENIX-4183 at 9/20/17 7:23 PM:
----------------------------------------------------------------

We'd like to give an error on an UPSERT that specifies it's own value for the ROW_TIMESTAMP column when the table has any mutable indexes. Let me adjust the summary of this JIRA, [~tdsilva], [~samarthjain].


was (Author: jamestaylor):
We'd like to give an error on an UPSERT that specifies it's own value for the ROW_TIMESTAMP column when the table has any mutable indexes. Let me adjust the summary of this JIRA.

> Disallow creating mutable indexes on tables with ROW_TIMESTAMP column
> ---------------------------------------------------------------------
>
>                 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 global mutable indexes. Immutable tables and indexes are fine, though.



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