Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Tue, 2 Aug 2016 07:18:20 +0000 (UTC)
From: "James Taylor (JIRA)" <jira@apache.org>
To: dev@phoenix.incubator.apache.org
Message-ID: <JIRA.12993481.1469781613000.196119.1470122300477@Atlassian.JIRA>
In-Reply-To: <JIRA.12993481.1469781613000@Atlassian.JIRA>
References: <JIRA.12993481.1469781613000@Atlassian.JIRA> <JIRA.12993481.1469781613146@arcas>
Subject: [jira] [Updated] (PHOENIX-3128) Remove extraneous operations during
 upsert with local immutable index
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 Aug 2016 07:18:24 -0000


     [ 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_v6.patch

Please review, [~rajeshbabu]. Other than for initial local index build, I don't believe there's any mechanism in place that generates the server-side updates for incremental index maintenance. So the first of the "extraneous operation" is actually required.

[~ankit@apache.org] - if this passes all tests and [~rajeshbabu] thinks it's fine, then we can commit this for 4.8.0. Otherwise, we can wait. Would be good to get a new RC up either way, though.

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