phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row
Date Mon, 08 May 2017 20:46:04 GMT

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

Lars Hofhansl commented on PHOENIX-3824:
----------------------------------------

[~vincentpoon], is getOldestTimestamp on a hot code path? It seems we're doing a sort O(N
logN) when we just need the minimum O(N), and it was O(1) before. (It's possible I am missing
something)

Looks good otherwise.

> Mutable Index partial rebuild adds more than one index row for updated data row
> -------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3824
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3824
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.10.0
>            Reporter: Vincent Poon
>            Assignee: Vincent Poon
>             Fix For: 4.11.0
>
>         Attachments: PHOENIX-3824.v1.patch, PHOENIX-3824.v2.patch
>
>
> If you follow this sequence:
> 1) disable index
> 2) write an updates to a data table row
> 3) trigger the BuildIndexScheduleTask partial rebuild
> then you end up with two index rows for the one data table row.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message