[
https://issues.apache.org/jira/browse/PHOENIX-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277711#comment-15277711
]
James Taylor commented on PHOENIX-2791:
---------------------------------------
+1. Looks good, [~tdsilva]. I agree, the view should be required to explicitly
set APPEND_ONLY_SCHEMA, otherwise it'll essentially be off for that view (even
if set on the parent). Basically, it has to be set all the way up the view
parent hierarchy to allow the optimization.
> Support append only schema declaration
> --------------------------------------
>
> Key: PHOENIX-2791
> URL: https://issues.apache.org/jira/browse/PHOENIX-2791
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Thomas D'Silva
> Labels: argus
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2791-v2.patch, PHOENIX-2791.patch
>
>
> If we know in advance that columns will only be added to but never removed
> from a schema, we can prevent the RPC from the client to the server when the
> client already has all columns declared in the CREATE TABLE/VIEW IF NOT
> EXISTS. To enable this, we can add an APPEND_ONLY_SCHEMA boolean flag to
> SYSTEM.CATALOG. Or another potential name would be IMMUTABLE_SCHEMA to match
> IMMUTABLE_ROWS?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
