phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3128) Remove extraneous operations during upsert with local immutable index
Date Sat, 30 Jul 2016 19:03:20 GMT


Hadoop QA commented on PHOENIX-3128:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit 3251ac58a6a9de890285ae82ba86d76618fa0a1c.
  ATTACHMENT ID: 12821169

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> 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.0
>         Attachments: PHOENIX-3128.patch, PHOENIX-3128_v2.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