You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2017/08/02 14:49:04 UTC

[jira] [Commented] (PHOENIX-4057) Do not issue index updates for out of order mutation

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

Lars Hofhansl commented on PHOENIX-4057:
----------------------------------------

Replication updates can sometimes come out of order.

> Do not issue index updates for out of order mutation
> ----------------------------------------------------
>
>                 Key: PHOENIX-4057
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4057
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0, 4.11.1
>
>         Attachments: PHOENIX-4057_v1.patch, PHOENIX-4057_wip1.patch
>
>
> Index maintenance is not correct when rows arrive out of order (see PHOENIX-4052). In particular, out of order deletes end up with a spurious Put in the index. Rather than corrupt the secondary index, we can instead just ignore out-of-order mutations. The only downside is that point-in-time queries against an index will not work correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)