[
https://issues.apache.org/jira/browse/PHOENIX-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226497#comment-16226497
]
Ankit Singhal edited comment on PHOENIX-4183 at 10/31/17 9:23 AM:
------------------------------------------------------------------
[~tdsilva], are there any done changes for this? I'm not able to locate the
related code.
was (Author: [email protected]):
[~tdsilva], are there any changes for this? I'm not able to locate the related
code.
> 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
> Labels: secondary_index
> 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 disallow creating an index on a mutable table that has a
> row_timestamp column.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
