You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/06/06 20:09:21 UTC
[jira] [Commented] (PHOENIX-2968) Reduce alter statement RPC when
table/view is set with APPEND_ONLY_SCHEMA and high value for
UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317129#comment-15317129 ]
James Taylor commented on PHOENIX-2968:
---------------------------------------
I don't understand this one. The degradation is due to the extra {{ALTER VIEW}} call. Is an acceptable solution to just not make that call since it's not needed? Or are you asking to optimize the {{ALTER VIEW}} call?
> Reduce alter statement RPC when table/view is set with APPEND_ONLY_SCHEMA and high value for UPDATE_CACHE_FREQUENCY
> -------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-2968
> URL: https://issues.apache.org/jira/browse/PHOENIX-2968
> Project: Phoenix
> Issue Type: Bug
> Reporter: Mujtaba Chohan
> Assignee: James Taylor
> Labels: Argus
>
> View is created with {{CREATE VIEW IF NOT EXISTS ... APPEND_ONLY_SCHEMA = true, UPDATE_CACHE_FREQUENCY=900000}}
> If {{ALTER VIEW <VIEW_NAME> ADD IF NOT EXISTS MYCOL VARCHAR}} is executed before each upsert statement then performance for each 1K batch upsert degrades by ~40X (50ms for 1K batch without alter statement vs 2300ms with alter statement)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)