You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2017/09/20 18:47:01 UTC

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

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

Thomas D'Silva commented on PHOENIX-4183:
-----------------------------------------

[~samarthjain] [~jamestaylor]

Should we allow using row timestamp feature for mutable tables and disallow creating indexes on them. Or should we disallow using row time stamp feature for mutable tables (which would allow users to create indexes)?

> 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)