You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2016/01/21 03:37:39 UTC

[jira] [Commented] (PHOENIX-2616) Indexes over immutable tables not marked as immutable

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

Samarth Jain commented on PHOENIX-2616:
---------------------------------------

[~jamestaylor] - should the upgrade query also update the sequence number for the index table row. Would the clients automatically start seeing the existing indexes as immutable otherwise? Also, would there be any impact on pre 4.7 clients if they start seeing the index also as immutable?

> Indexes over immutable tables not marked as immutable
> -----------------------------------------------------
>
>                 Key: PHOENIX-2616
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2616
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2616.patch
>
>
> We're not marking indexes as immutable when they're on an immutable table. This causes us to do conflict detection when we're building the index which is expensive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)