phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index
Date Tue, 02 Aug 2016 06:45:20 GMT

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

James Taylor commented on PHOENIX-3128:
---------------------------------------

It only fails for a LOCAL INDEX on testTableV when we don't send the index updates from the
client. Any ideas, [~lhofhansl], [~rajeshbabu]? In theory, we shouldn't need to send the updates
for local indexes as they can be generated locally on the server side.

> 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_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)

Mime
View raw message