[
https://issues.apache.org/jira/browse/PHOENIX-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3128:
----------------------------------
Attachment: PHOENIX-3128_v7.patch
Here's a more cleaned up patch, [~rajeshbabu]. FWIW, I don't think we need to
prevent sending over the client mutations for local indexes in 4.8.0. I think
this patch is worthwhile (if the tests pass), though, as it prevents the
server-side scan for immutable tables when we don't need to know the values of
the prior row.
> 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.1
>
> 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_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)
