[
https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416686#comment-15416686
]
James Taylor commented on PHOENIX-3128:
---------------------------------------
There are Gets done on the server side to lookup the prior value of a row that
should no longer be done. Maybe you can confirm, [~rajeshbabu]? The overhead of
index maintenance for local immutable indexes should be much lower (maybe 30%
lower).
> Remove extraneous operations during upsert with local immutable index
> ---------------------------------------------------------------------
>
> Key: PHOENIX-3128
> URL: https://issues.apache.org/jira/browse/PHOENIX-3128
> Project: Phoenix
> Issue Type: Bug
> Reporter: Junegunn Choi
> Assignee: Junegunn Choi
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3128.patch, PHOENIX-3128_v2.patch,
> PHOENIX-3128_v3.patch, PHOENIX-3128_v4.patch, PHOENIX-3128_v5.patch,
> PHOENIX-3128_v6.patch, PHOENIX-3128_v7.patch, PHOENIX-3128_v8.patch,
> PHOENIX-3128_wip.patch
>
>
> Upsert to a table with a local immutable index is supposed to be more
> efficient than to a table with a local mutable index, but it's actually
> slower (in our environment by 30%) due to extraneous operations involved.
> The problem is twofold:
> 1. Client unnecessarily prepares and sends index update.
> 2. Index cleanup is done regardless of the immutability of the table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
