phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index
Date Tue, 02 Aug 2016 07:18:20 GMT


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.

[] - 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:
>             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

View raw message