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 2016/12/05 21:13:58 UTC

[jira] [Commented] (PHOENIX-3445) Add a CREATE IMMUTABLE TABLE construct to make immutable tables more explicit

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

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

[~jamestaylor]

Thanks for the feedback. For indexes and views in createTableInternal() the immutable table flag is automatically set based on the parent table immutability, the immutable table property is only used for regular tables. 

To support changing immutability of older tables, should we only allow changing immutability of a table using ALTER TABLE only if the storage scheme is ONE_CELL_PER_KEYVALUE_COLUMN? 
I will deprecate the IMMUTABLE_ROWS table property. Should we also deprecate the "phoenix.mutate.immutableRows" property and remove it in the next major release?

Currently we just default to the four bytes encoding scheme. I created PHOENIX-3519 to specify the QualifierEncodingScheme in the Create Table statement. 

> Add a CREATE IMMUTABLE TABLE construct to make immutable tables more explicit
> -----------------------------------------------------------------------------
>
>                 Key: PHOENIX-3445
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3445
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Samarth Jain
>            Assignee: Thomas D'Silva
>         Attachments: PHOENIX-3445.patch
>
>




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